Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 7ff86583279b3061…

MALICIOUS

RTF / .DOC

150.5 KB First seen: 2024-05-22
MD5: de28e76dce38059a0331562a9579106e SHA-1: 6f6cb90b7a374f34edda30c9654d6aad4759925e SHA-256: 7ff86583279b30615f6ef62b356c10a1f2f203d6e5437f6632236219e27fcc3c
160 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.005 Visual Basic

The file is an RTF document containing an embedded OLE object, specifically identified as an Equation Editor exploit. The document body includes a lure instructing the user to 'Enable editing' to bypass macro security. This combination strongly suggests the document is designed to exploit a vulnerability via the OLE object when the user is tricked into activating it.

Heuristics 5

  • 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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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_off00008f7e.bin
f09bcbd12229c50e85c71d06f735db60b7064b6ab0bf001df9533f7c0a7a3389
rtf-objdata-decoded RTF \objdata at offset 0x8F7E 2096 bytes