Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 bf46d7d5610219e0…

MALICIOUS

RTF / .DOC

3.8 KB
MD5: bab7509e240fa0117801fa86886d8011 SHA-1: bc0b7a5604b8bcf572040bbc5b4ea50020430eab SHA-256: bf46d7d5610219e07112e1f985a51f2234ed7a8e2c0d736a080bfd54ecc5bbcf
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF document contains embedded OLE object data, specifically triggering critical heuristics related to Equation Editor exploitation. The \objupdate directive indicates that the embedded OLE object is designed to activate automatically upon opening, leading to the execution of arbitrary code. This is a common delivery mechanism for exploiting vulnerabilities like CVE-2017-11882.

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_off000000e7.bin
ad643e269c35699da7f192ce99edd83f57b87ecbe54fa13e4190d013f6b7512f
rtf-objdata-decoded RTF \objdata at offset 0xE7 1638 bytes