Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 46497a6346d59fa1…

MALICIOUS

RTF / .DOC

3.8 KB
MD5: 968d55d950eb3f94db59dcff3b02735e SHA-1: 07d5b40d1863c6b77660f47c3f5802b6e6f3d9bb SHA-256: 46497a6346d59fa194e560ab6b25ac7e002b3704ef7cc7c4d9ba0470bad08394
160 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF file contains embedded OLE objects, specifically triggering heuristics related to Equation Editor vulnerabilities and automatic OLE object activation. This indicates the file is designed to exploit a known vulnerability in the Equation Editor component to achieve arbitrary code execution upon opening. The presence of ".objupdate" further suggests an attempt to force the activation of the embedded object. The attack pattern is consistent with exploiting a vulnerability to deliver a malicious payload.

Heuristics 4

  • 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.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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
82556202fff3cf1008b0c535dc59652fce36041dc4b15407d5bc9267803b82b7
rtf-objdata-decoded RTF \objdata at offset 0xB6 1619 bytes