Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 d7ee90c9e4672420…

MALICIOUS

RTF / .DOC

14.7 KB
MD5: 0285634d458ab2befb2eda5bb95fdfaa SHA-1: b27c409117b620d29750ad1ae5c7a912c1c8b9c7 SHA-256: d7ee90c9e467242056847b0191fffea57a5ac0ada521c2ba1d405abcf56c87b7
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.001 User Execution: Malicious Link T1203 Exploitation for Code Execution

The sample is an RTF document that contains OLE object data and triggers an objupdate event, indicating it's designed to activate embedded objects. The critical heuristic RTF_EQUATION_EDITOR specifically points to a known vulnerability in the Equation Editor component, which is commonly exploited to achieve arbitrary code execution. This allows the document to act as a dropper for further malicious activity, likely downloading and executing a second-stage payload.

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_off00000be3.bin
bc01b75dc255a3827d440102adec6dc96810994f031f78ae5b955e8d3cb94559
rtf-objdata-decoded RTF \objdata at offset 0xBE3 2005 bytes