Malicious RTF — malware analysis report

Static analysis result for SHA-256 29477d6a88056748…

MALICIOUS

RTF

67.7 KB First seen: 2020-02-04
MD5: b98faec79c0a59ebedc2e958b4db3d82 SHA-1: ab16490af4fb82b976bec4d65d76ca939190de38 SHA-256: 29477d6a880567483a743acc561032e217939d85961e587f759b38964d764e46
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 2538 bytes
SHA-256: c2acc1429b51cc26386227286dcd107d7ac0140ed5812a15cf0cfe4698b91777