Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 01ecdb1502c3c5fc…

MALICIOUS

RTF / .DOC

20.9 KB
MD5: d84a927f66f6183e62ae013237a5a577 SHA-1: 67133356213a4821dfcb1e41f538fc8d3a688314 SHA-256: 01ecdb1502c3c5fc3984be69720eb1a2b69abc3ef847282b6ec4b3662767d455
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The sample is an RTF document that contains embedded OLE objects and specifically triggers heuristics for the Equation Editor vulnerability. This indicates it's designed to exploit CVE-2017-11882, a common method for initial execution. The presence of \objupdate further suggests an attempt to force OLE object activation, leading to code execution. The likely goal is to download and execute a secondary payload, though no specific URLs or further stages were extracted from this sample.

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_off00001071.bin
0fa6ffd87a3a514a8e960368e7060006129f0249fc39ce45c4c723aacf403702
rtf-objdata-decoded RTF \objdata at offset 0x1071 1767 bytes