Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 d18da684313ab3fe…

MALICIOUS

RTF / .DOC

4.7 KB
MD5: e8453860de1826d58e0f5de9e04f11ea SHA-1: ac2e4b588051a6ba7bcef104e7027f9ce1036b14 SHA-256: d18da684313ab3fe2b403fca933096ce347b800ef94b5a71dfc8e3a607f95dcd
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1559.002 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 numeric 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_off000000b9.bin
3ffe749c4c75d7833017a931127d625fca8a17e2711d27eaa70288717dcbcebf
rtf-objdata-decoded RTF \objdata at offset 0xB9 2067 bytes