Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 faa7ea2d06a9cc4a…

MALICIOUS

RTF / .DOC

14.3 KB
MD5: 32bbcbd045d8904910ef206573a80ef9 SHA-1: bcfbcb78c1fab958b0e8a6e00af4e7a8e8e7080d SHA-256: faa7ea2d06a9cc4aa49b7b3a126b4cfa5d6f64b495d9562582574ad727e93fd6
160 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1059.001 PowerShell

The sample is an RTF document that contains embedded OLE objects, specifically triggering heuristics related to Equation Editor exploitation. The presence of \objupdate and \objdata directives strongly suggests that the document is designed to automatically activate the embedded object upon opening, leading to the execution of arbitrary code. This is a common technique for delivering malware via document exploits.

Heuristics 4

  • Split hex Equation Editor ProgID + OLE object critical RTF_EQUATION_EDITOR
    RTF embeds the Equation.3 ProgID as hex bytes near OLE object activation and splits the byte stream with whitespace or an ignorable RTF group. This is an Equation Editor OLE activation surface commonly used by CVE-2017-11882 / CVE-2018-0802 exploit documents.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \objupdate forces OLE activation high RTF_OBJUPDATE
    RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000bf5.bin
baae629e7e1ec6e3753a4325b338e662ceda55f268fd337f091f3c7e0eb605a5
rtf-objdata-decoded RTF \objdata at offset 0xBF5 1568 bytes