Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 a2907290b9082b13…

MALICIOUS

RTF / .DOC

4.0 KB
MD5: 40ea0fffa22299ee4236a5118660a9b7 SHA-1: 3fd4bada7bcd6848ba42b674ca6bc7b25efb75e1 SHA-256: a2907290b9082b133e5f4d82407976db26620a692834195cbf6a334061c76367
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1559.001 Component Object Model Hijacking

The RTF document contains embedded OLE object data and specifically triggers the Equation Editor vulnerability. The ".objupdate" directive forces the activation of the embedded OLE object, which is a known method for exploiting the Equation Editor vulnerability to achieve arbitrary code execution. No scripts were extracted, and the document body contained only numerical data, providing no further context on the payload.

Heuristics 3

  • 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.
  • \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_off000000aa.bin
010b4336d42de3d2ea419b948732de6758fbb798acb3bbc507211a5a2f8ed5eb
rtf-objdata-decoded RTF \objdata at offset 0xAA 1713 bytes