Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 db816f7570e6d5ca…

MALICIOUS

RTF / .DOC

4.4 KB
MD5: 9b6b14a511973e0f59718177f0717ea8 SHA-1: 9f9c117498d2091be0cbaf8c5611c734e489d365 SHA-256: db816f7570e6d5cae4d48653f2fdcf366b1deb35833d111a69fff1c1069c3c3b
120 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Phishing: Spearphishing Attachment

The RTF document contains embedded OLE objects, specifically triggering a critical heuristic for a split hex Equation Editor ProgID. This indicates the document is designed to exploit a known vulnerability in the Equation Editor component, likely leading to arbitrary code execution. The presence of \objupdate further suggests that the embedded object is intended to be activated automatically upon opening the document.

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_off00000091.bin
f9c6754b69a949462d9fd6ce857c1c7e868e8e15655b209b125ad007ba131a5b
rtf-objdata-decoded RTF \objdata at offset 0x91 1955 bytes