Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 071168bc1a6f318a…

MALICIOUS

RTF / .DOC

50.8 KB
MD5: f1ec0ae65d22782e09879b1c3d4c0df9 SHA-1: 12ec5664f98f3de2224685c85a27b12cf0244aac SHA-256: 071168bc1a6f318a8f4de567a6c75b0fbc5340802475c433da04e30a7c0af0c9
120 Risk Score

Malware Insights

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

The sample is an RTF document that contains an embedded OLE object, specifically targeting the Equation Editor. Heuristics indicate that \objupdate forces OLE activation, which is a known method for exploiting vulnerabilities like CVE-2017-11882. This exploitation likely leads to the execution of a secondary payload, although the specific payload and its origin could not be determined from the provided evidence.

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_off00000ac9.bin
96dd2c27db2048fc81b0481490fb7e7edb07cbea14acaf1245fa789c86b60428
rtf-objdata-decoded RTF \objdata at offset 0xAC9 2104 bytes