Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 a0f83ac12ac70862…

MALICIOUS

RTF / .DOC

4.2 KB
MD5: 5dbc2e24ad18fb46139eb06b458be9e4 SHA-1: 1872a3c9e43ea888436e8b1c99c6ff773d6efac3 SHA-256: a0f83ac12ac70862e8d23f203dfacab3cb6b7db722caaf54a0316c9c036c67d4
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 heuristics related to Equation Editor exploitation. The \objupdate directive indicates an attempt to force OLE activation, which is a common technique for exploiting vulnerabilities like CVE-2017-11882. This suggests the file is designed to execute arbitrary code upon opening.

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_off000000e6.bin
6a1907c58d9462e05176ca87b14f5e707d012f0563007b3fcb1beb031afd76f9
rtf-objdata-decoded RTF \objdata at offset 0xE6 1922 bytes