Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 f2c7b0be851fa6fd…

MALICIOUS

RTF / .DOC

4.0 KB
MD5: 3b9477bae50b600aa581e67c68206f73 SHA-1: 0e826ae08ac2c3e3367ea6f55fff32f4ddadd2b8 SHA-256: f2c7b0be851fa6fd143e0b965bb056f4de5fc8d0e41bb553892f33038bae8e8f
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1559.002 Component Object Model Hijacking

The RTF document contains embedded OLE objects, specifically triggering the Equation Editor vulnerability. The presence of ".objdata" and ".objupdate" directives strongly suggests an attempt to exploit this component, leading to arbitrary code execution. No specific family could be identified, and no further IOCs were extracted.

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_off00000084.bin
4e61b234fb6bfb3f3bbf23547623bcc686c3119281002335109a0a16a2ad1154
rtf-objdata-decoded RTF \objdata at offset 0x84 1873 bytes