Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 df6404eb3887ba29…

MALICIOUS

RTF / .DOC

3.8 KB
MD5: e7ad0749d91263a6d56f9ecc14004f7f SHA-1: 4aefac0e8ec6c16cf123e2621e804e01a9535098 SHA-256: df6404eb3887ba291df34a478e12ee58bf5529c5eee8688b9f6b99bb7f52c09d
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1559.001 Component Object Model Hijacking

The RTF document contains embedded OLE object data, specifically triggering a critical heuristic for the Equation Editor vulnerability. The \objupdate directive forces OLE activation, indicating an attempt to exploit this vulnerability for code execution. The presence of multiple \objdata sections further supports the exploitation of embedded objects.

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_off000000bc.bin
93e1125d9fdda78cdd2d0a5fbc9ae0178dd802b8c94d79587d40c62a5c237341
rtf-objdata-decoded RTF \objdata at offset 0xBC 1632 bytes