Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 6268b4d14af382d2…

MALICIOUS

RTF / .DOC

4.5 KB
MD5: 78001af866ffc34a0a903d7df7dc911d SHA-1: b9dabef40c0d6c6c6dd6c830f10e3546caa09d37 SHA-256: 6268b4d14af382d2e100b4d2c1b7b52b328378c3af21ad4760a68effebba109f
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF document contains embedded OLE objects and specifically triggers heuristics for the Equation Editor vulnerability. This indicates the file is designed to exploit a known vulnerability to achieve code execution upon opening. The presence of ".objupdate" further suggests an attempt to force OLE object activation, likely to trigger the exploit.

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_off00000083.bin
e054dde71f7ea5584a04cb7cdcc654fedf0730fcb381b1e72c5e5b29aa594eb5
rtf-objdata-decoded RTF \objdata at offset 0x83 2019 bytes