Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 3eb7d51b8bc7bca2…

MALICIOUS

RTF / .DOC

14.0 KB
MD5: 1f20821a142f93fac5153746b902b166 SHA-1: c111910378b25573ed386bbdedd160efe0c441d1 SHA-256: 3eb7d51b8bc7bca27400be167b265335d205e8936312d1b33c2c3dab04385d15
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Phishing: Spearphishing Attachment T1204.002 Malicious File: User Execution

The sample is an RTF document that contains embedded OLE object data and triggers an objupdate event, indicating it's designed to activate embedded content. Crucially, it fires the RTF_EQUATION_EDITOR heuristic, which signifies the exploitation of a known vulnerability in the Equation Editor component. This technique is commonly used to download and execute a second-stage payload, leading to a malicious outcome.

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_off00000fe0.bin
9413046d24af726e8177398956dc76c7548961b770ef7d10483b6829892fd875
rtf-objdata-decoded RTF \objdata at offset 0xFE0 1810 bytes