Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 6eaf2e8598e55c3e…

MALICIOUS

RTF / .DOC

41.1 KB First seen: 2023-07-26
MD5: 21e08176b04b091f010d1806549c080a SHA-1: ce6d96a71214d95416a4e43f1abf260cc0a2493c SHA-256: 6eaf2e8598e55c3e4f6c5040411f20a2c91948023c69c08a6c65434b54bb0354
140 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains an embedded OLE object with a split Equation Editor ProgID and an objupdate directive, indicating an attempt to exploit a known vulnerability. The document body includes a lure instructing the user to 'Enable editing', a common tactic for macro-based malware droppers. The presence of these elements strongly suggests the file is designed to exploit the Equation Editor vulnerability to execute a malicious payload.

Heuristics 4

  • 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 1 \objdata section(s) — embedded OLE objects
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000059db.bin
e652b4f62847686e3f61942999eaff22165ea1b67141f59a73c0e0751c6b05b5
rtf-objdata-decoded RTF \objdata at offset 0x59DB 1395 bytes