Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 bd92d6bc139f26db…

MALICIOUS

RTF / .DOC

4.1 KB
MD5: 7695321cdd92ac0e205ecfc16e7db676 SHA-1: 0484b8ce98160be72291f0eaac95f2549159b90a SHA-256: bd92d6bc139f26dbf58bed3b560730b241974cc5d2195958a24c437b754df599
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, indicating exploitation of a known vulnerability. The ".objupdate" directive forces OLE activation, leading to arbitrary code execution. No further details on the payload or specific exploit are available from the static analysis.

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_off000000b4.bin
de089edb538ce90f80e7c0454899c6a237929ea0059110f2f4287be8b98c552d
rtf-objdata-decoded RTF \objdata at offset 0xB4 1771 bytes