Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 f9709f9062aeee6d…

MALICIOUS

RTF / .DOC

11.5 KB
MD5: 713cb7783925212be14597a0ab6fe787 SHA-1: e1ddd4fc618377da84922f6eb16aa684816dbfcf SHA-256: f9709f9062aeee6d34a0fc613e3f9356b2d95289c0780d2ab28ad84e2faadd17
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1059.001 PowerShell

The sample is an RTF document containing OLE object data, specifically triggering critical heuristics for Equation Editor exploitation and OLE object activation. This indicates the document is designed to exploit a vulnerability, likely CVE-2017-11882, to achieve code execution. The embedded OLE object data is the primary mechanism for this exploit. The attack pattern is consistent with delivering a secondary payload via the exploited 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_off000006b6.bin
9e1ba2ad3f96c11585e597460ed2bee0524d7a9f989746cdad6ffd1fc7859bb6
rtf-objdata-decoded RTF \objdata at offset 0x6B6 1331 bytes