Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 0631de7652344b36…

MALICIOUS

RTF / .DOC

15.4 KB
MD5: 9f1f2eefaac64b1029574050e16c4d49 SHA-1: a9f747b6159d9f5513a3c45c034339a0750c2669 SHA-256: 0631de7652344b360019ee273589f1adc811e2511bfd80d77e45ce6203815e74
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF document contains embedded OLE object data, specifically a decoded Equation Editor payload. The \objupdate directive forces OLE activation, indicating an attempt to exploit a vulnerability. This exploit likely leads to the execution of a second-stage payload, as suggested by the critical RTF_EQUATION_EDITOR heuristic.

Heuristics 3

  • Decoded Equation Editor payload + PE critical RTF_EQUATION_EDITOR
    RTF decodes to an Equation Editor ProgID adjacent to OLE activation and the same decoded object stream contains embedded PE bytes. This matches the Equation Editor exploit surface used by CVE-2017-11882 / CVE-2018-0802 documents, while requiring payload evidence to avoid flagging benign Equation references.
  • \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_off0000148b.bin
7ea691fd04163f49543e27f105ead8f7d5379845e9876352a279f3072146b94f
rtf-objdata-decoded RTF \objdata at offset 0x148B 1502 bytes