Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 6f2bfc4417cf4ce6…

MALICIOUS

RTF / .DOC

4.4 KB
MD5: 33fbe50892174bbe15c4fc65254e9063 SHA-1: 67ec5e09eabbfe9e512b2973c9810e41b86f329a SHA-256: 6f2bfc4417cf4ce6049248941da5e4acdfbaf89d60da8647ced40f45ca2d874c
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE object data and specifically triggers the RTF_EQUATION_EDITOR heuristic, indicating exploitation of the Equation Editor vulnerability. The ".objupdate" directive further suggests that the embedded object is designed to be activated, leading to arbitrary code execution. This is a common method for delivering malicious payloads via spearphishing attachments.

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_off000000bc.bin
d29ebb0b56bdde28ef049ce4fe72122c25314874195cc7b9569cf93c7417e964
rtf-objdata-decoded RTF \objdata at offset 0xBC 1924 bytes