Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 5de747fb59ea1597…

MALICIOUS

RTF / .DOC

19.0 KB
MD5: dd2994252e775d7fd7a747d3e35903e0 SHA-1: abc338af61e91c173d7020ab63fe3f409bb545ea SHA-256: 5de747fb59ea15979053e71999fce0efc622618aef43e702b3d0dd22a7650dac
120 Risk Score

Malware Insights

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

The sample is an RTF document containing an embedded OLE object with a split Equation Editor ProgID, triggering critical heuristics for exploitation. The \objupdate directive further indicates an attempt to force OLE activation. This combination strongly suggests exploitation of a known Equation Editor vulnerability (CVE-2017-11882 or similar) to achieve code execution, likely for downloading and running a subsequent stage.

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 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001408.bin
f29b1e9815565b1ce30771ec5414173bf603b0e4e10de935b2d72751c973b012
rtf-objdata-decoded RTF \objdata at offset 0x1408 1432 bytes