Malicious RTF — malware analysis report

Static analysis result for SHA-256 e75581c4a16ed2df…

MALICIOUS

RTF

66.4 KB First seen: 2019-03-10
MD5: 33568514b71dabfa81022a45b7888693 SHA-1: a571523deda74977196825652a103fe936650ec6 SHA-256: e75581c4a16ed2dfb78e413e385f6155fa00f032330607e3ffa8a502ad1d185b
120 Risk Score

Malware Insights

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

The RTF file contains critical heuristics indicating the exploitation of the Equation Editor vulnerability (RTF_EQUATION_EDITOR) and forces OLE activation (RTF_OBJUPDATE). This suggests the file is designed to execute arbitrary code upon opening, likely to download and run a secondary payload. The presence of OLE object data further supports this execution vector.

Heuristics 3

  • Split hex Equation Editor ProgID + OLE object critical CVE likely 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_off0000144c.bin rtf-objdata-decoded RTF \objdata at offset 0x144C 2536 bytes
SHA-256: 88e4a2b2063bb8022f84a97f5822f789aad7f1b4c5d2ceaf9a7d9f1fea006e73