Malicious RTF — malware analysis report

Static analysis result for SHA-256 db270031d1e90e47…

MALICIOUS

RTF

13.5 KB
MD5: d56fc97e3c1b99d076635216669d34e4 SHA-1: 716e3ae950a2bc9be7d8ef9d08405775c240178d SHA-256: db270031d1e90e47da09d9cd7827ed9c748d07699149750026a571e8027ea00a
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The file is an RTF document containing an embedded OLE object that exploits a known vulnerability in the Equation Editor. The heuristics indicate that \objupdate forces OLE activation, which is a common technique for exploiting this vulnerability. The presence of OLE object data and the specific Equation Editor exploit strongly suggest a malicious intent, likely to download and execute a second-stage payload.

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_off00001dc4.bin
9a00e743fdbb602413cb0e6d9092c460e181ad76c6efc40588f3416ab14b26c6
rtf-objdata-decoded RTF \objdata at offset 0x1DC4 1897 bytes