Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 d502f449e20dfad4…

MALICIOUS

RTF / .DOC

4.8 KB
MD5: 69346f1049bfff5e0c6e9c9ea39bda61 SHA-1: 4aed744d04b6de773f3c4fce1aabf6db22a1e833 SHA-256: d502f449e20dfad4bda71d37c5f0c6f4c5e44df76682b791f63e329188adbc04
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 critical heuristics related to Equation Editor exploitation. The presence of \objupdate further indicates that the embedded object is designed to be activated automatically upon opening, leading to the execution of malicious code. This pattern is commonly associated with exploiting vulnerabilities like CVE-2017-11882 to achieve arbitrary code execution.

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_off000000b6.bin
9a186c894e4d5769356164cec8853344b75566a0a5a69f5409826c65073f9d51
rtf-objdata-decoded RTF \objdata at offset 0xB6 2161 bytes