Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 0e4f3dabe2b20f4d…

MALICIOUS

RTF / .DOC

17.6 KB
MD5: f874f1615ac7b6910b37f82e9ff901da SHA-1: 577033d813986df279de939ebbcaac94d1fdcb03 SHA-256: 0e4f3dabe2b20f4d4d22e1e8f8f7548383d6f5cbaf0073d91f2aae44655a31c1
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The sample is an RTF document containing OLE object data and triggering heuristics for Equation Editor exploitation. The \objupdate directive forces OLE activation, indicating an attempt to execute embedded code. This strongly suggests the file is designed to exploit a vulnerability, likely CVE-2017-11882, to achieve arbitrary code execution for downloading and running a secondary payload.

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_off00001fc5.bin
89142ce95a4d0e04879b87709d6b58cf437c88ca6b988d0fe4f2b0ff1202a8ec
rtf-objdata-decoded RTF \objdata at offset 0x1FC5 1302 bytes