Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 be14b7f860ecdf2f…

MALICIOUS

RTF / .DOC

4.7 KB
MD5: 4214190ad234825c5019989942869a8e SHA-1: 07ec7b874223fe974e737884b48c6f0164b81007 SHA-256: be14b7f860ecdf2ffdf4942bacabe4757714d7e0c9b8b7e6a8f958981154329f
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 presence of ".objupdate" indicates that the embedded OLE object is designed to be activated automatically, leading to the exploitation of the Equation Editor vulnerability for arbitrary code execution. No scripts were extracted from this sample.

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_off0000009e.bin
6aa08d68644a0bbb0dfdc976560e53f38c48c59f7d962187cfc7bc0f3f5d538d
rtf-objdata-decoded RTF \objdata at offset 0x9E 2177 bytes