Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 9d13dad91f0eb4b7…

MALICIOUS

RTF / .DOC

4.1 KB First seen: 2022-03-23
MD5: 717ffdf7e6a6b539781bca9a62041979 SHA-1: 65f9c9e1e6ec56d7a12b6e6f170e0a13e9637800 SHA-256: 9d13dad91f0eb4b78f4e76cc27f8bbb9aa4bc61f37634b60440ee6d05bb13353
121 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, specifically triggering the Equation Editor vulnerability. The \objupdate directive forces OLE activation, indicating an attempt to exploit this vulnerability for code execution. The presence of multiple \objdata sections further supports this. No specific malware family is identifiable from the available heuristics.

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_off000000bb.bin
db39a212f480f8ba413c31315dd743cf8e8b47794c7bc09cd94d8f7be3ca81bc
rtf-objdata-decoded RTF \objdata at offset 0xBB 1811 bytes