Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 57954b53a0617157…

MALICIOUS

RTF / .DOC

3.9 KB
MD5: 065093b34ba513f24662a50066b43d54 SHA-1: b1c68e468658e0c65ebde9187c7e57f3123aee72 SHA-256: 57954b53a06171571be95772b77cff9c1fe257f1c787d3bc3479441a4337e7aa
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 the embedded OLE object, which is likely to contain a malicious payload exploiting the Equation Editor vulnerability to achieve code execution.

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_off000000d3.bin
03a556b0d9c35f6b1ac668d2410cd249bc0c04f589523f05d61acdfb570706ed
rtf-objdata-decoded RTF \objdata at offset 0xD3 1775 bytes