Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 e70da947a0b16e3a…

MALICIOUS

RTF / .DOC

3.9 KB
MD5: 94f6f47f76ae0abffae2e07f705e765f SHA-1: 1b2227210fcd649d6e720d8b660314f18442df85 SHA-256: e70da947a0b16e3a9e70d021bf117ed49eba5389319439742096626b30b91f19
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains embedded OLE object data and specifically triggers the Equation Editor vulnerability. The ".objupdate" directive forces the activation of this embedded object, leading to arbitrary code execution. This is a common delivery mechanism for exploiting the Equation Editor vulnerability.

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_off0000009f.bin
4e79926a9aa4f78559d02b63f749f6967d7f489786b24171eb7f5dc099fa4380
rtf-objdata-decoded RTF \objdata at offset 0x9F 1719 bytes