Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 546d6020b28de166…

MALICIOUS

RTF / .DOC

4.5 KB First seen: 2021-09-17
MD5: 179d3fd14f67e1b6ea026198fbdeb677 SHA-1: b9cda110fff869d29778accc0db0ceb8040f6a85 SHA-256: 546d6020b28de1666c68a2b9313bf824155d65350eaab039d919a8446db4965c
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE object data and triggers an ".objupdate" directive, indicating an attempt to exploit the Equation Editor vulnerability. This is a common technique for delivering malicious payloads. The critical heuristic firing on RTF_EQUATION_EDITOR strongly suggests exploitation of CVE-2017-11882.

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_off000000bf.bin
715b61713d92213bc591a093706fe81e42fae5b2a6a7ed88534135b8886913d1
rtf-objdata-decoded RTF \objdata at offset 0xBF 1968 bytes