Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 642bd8874817dd63…

MALICIOUS

RTF / .DOC

4.2 KB
MD5: 95e0d5aae59f18eb2974faa43de306d9 SHA-1: 7aed3c77609e97fb8c6e2ae2f21a319be03c90c5 SHA-256: 642bd8874817dd63014b4be090b417c2b89fdac330057706a90462296b9136db
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 the RTF_EQUATION_EDITOR heuristic, indicating exploitation of a vulnerability within the Equation Editor component. The ".objupdate" directive further suggests an attempt to force OLE object activation, leading to arbitrary code execution. This is a common technique for delivering malicious payloads via document attachments.

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_off00000086.bin
79b08954833a4ac678f25b13281b2feec16aa27c4a2cbb4b1eb2d58db5729bc2
rtf-objdata-decoded RTF \objdata at offset 0x86 1973 bytes