Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 714404da6e6ac2f6…

MALICIOUS

RTF / .DOC

65.4 KB
MD5: e21986b29ed37be44583aae2308af473 SHA-1: ced1cee9b0fdb3d7012590b0d79b0b577be931a8 SHA-256: 714404da6e6ac2f6ca0aa7303b94230c0d2be27273d78fb0aa16a6796d4f7c26
120 Risk Score

Malware Insights

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

The sample is an RTF document containing embedded OLE objects and specifically triggers heuristics for the Equation Editor vulnerability. The \objupdate directive forces OLE activation, indicating an attempt to exploit this vulnerability for code execution. This is a common method for delivering secondary payloads.

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_off0000113a.bin
60bc5bcecd3f85ae7f11c847c713f59f53d3eb6e2ee08cddbfee3319a06d359c
rtf-objdata-decoded RTF \objdata at offset 0x113A 1801 bytes