Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 c4d3907dc8879797…

MALICIOUS

RTF / .DOC

27.5 KB First seen: 2022-12-12
MD5: 3aa28be320fba95784a735b68bea2064 SHA-1: af24831666a34ebdfaa35d5fe129794149c31e67 SHA-256: c4d3907dc8879797d5da20449398ee4cabec83bcc44a0a61694fcf10c581022f
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 specific Equation Editor ProgID, identified by the RTF_EQUATION_EDITOR heuristic. The RTF_OBJUPDATE heuristic indicates that the object is configured to activate automatically upon opening, and the SE_ENABLE_LURE heuristic confirms the presence of a prompt to enable editing, a common social engineering tactic. This suggests the document is designed to exploit a vulnerability, likely within Equation Editor, to execute a 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_off00004243.bin
e1608ce5bd6ad778c17dccc31a89940cbf8f4e37ca93353bc848f2599cd57ce3
rtf-objdata-decoded RTF \objdata at offset 0x4243 1707 bytes