Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 936837d58eafac52…

MALICIOUS

RTF / .DOC

3.1 KB
MD5: e61b3849f4eccac9531e82466c663e84 SHA-1: 2d91eae655bf7c8bc6036d1e0bd2614892fdcf59 SHA-256: 936837d58eafac529ab83d47efc08d77e5d821f7fcafbb2f207662c3d5b54a49
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 and specifically triggers the Equation Editor vulnerability. The ".objupdate" directive forces the activation of the embedded OLE object, which is likely to contain a malicious payload designed to exploit the Equation Editor vulnerability for arbitrary code execution.

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_off00000096.bin
e9006874c284206aa685ca36279a4d0e69611179cdfba5412b7a3117e8c494e1
rtf-objdata-decoded RTF \objdata at offset 0x96 1348 bytes