Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 039dd5bcf3eeb084…

MALICIOUS

RTF / .DOC

3.7 KB
MD5: 46231727958e6b8bf2f2af9eb1883ee4 SHA-1: ee13a45718a614a5512ca289ecc60755561b2ae0 SHA-256: 039dd5bcf3eeb08484663983831f1b6c61fcacb35a96041ab11e22855f262023
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 Equation Editor vulnerability. The ".objupdate" directive forces the activation of the embedded OLE object, which is likely to contain a malicious payload. This technique is commonly used to achieve arbitrary code execution on the victim's machine.

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_off000000ac.bin
d42870028a158edefc189f20f99572f60ac4ada5a504ebac12236e72f42b2165
rtf-objdata-decoded RTF \objdata at offset 0xAC 1598 bytes