Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 321b03d3c4768e07…

MALICIOUS

RTF / .DOC

3.4 KB
MD5: 99cae3d2f9cc122437e94796f4fba799 SHA-1: c83d8e3329854f14980b49f916e26a1e85566468 SHA-256: 321b03d3c4768e0748ce8995922b5c1ef0b8b7be39a2c2bd94402f39212e19f1
120 Risk Score

Malware Insights

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

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 designed to exploit the Equation Editor. This indicates the document is likely a lure to deliver a malicious payload via a known 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_off0000008a.bin
1cd36421c3a0741bae5935b12798c0c79479c3a59d5509895d7a6b1460dc8da1
rtf-objdata-decoded RTF \objdata at offset 0x8A 1563 bytes