Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 7a13cc342d0c6742…

MALICIOUS

RTF / .DOC

3.6 KB
MD5: 7574e59a8c06150dd3224ac2dafd95ee SHA-1: f29b6a7a9e65b8ebe4167685db51190cdde15f01 SHA-256: 7a13cc342d0c67425280aabfe4797e4baacfc94f4b042d26ae64e9e488190e61
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, specifically triggering critical heuristics related to Equation Editor exploitation. The presence of \objupdate further indicates an attempt to force OLE activation, 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_off000000c3.bin
2067c41c280ee9458175236c5daac7b868c26c43ced7050528dddd296bf50dd3
rtf-objdata-decoded RTF \objdata at offset 0xC3 1665 bytes