Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 3cc17a69edf1def4…

MALICIOUS

RTF / .DOC

4.1 KB
MD5: 42b480abf9dc4ebc517afc981904b7ed SHA-1: 629332554774d011bcaf99eb9457709e7202a68a SHA-256: 3cc17a69edf1def4ce241615dac2e2f15359c6d4572744e7e7d5f262d230c03f
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.003 Windows Command Shell

The RTF document contains embedded OLE object data and triggers an object update, indicative of an exploit. Specifically, the RTF_EQUATION_EDITOR heuristic points to the use of a known vulnerability in the Equation Editor component. This suggests the document is designed to exploit this vulnerability upon opening, likely leading to 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_off00000090.bin
c92515177a11982b5a06060e8659c0ccfdf5180ddce6aafb05899b1e0fb757bf
rtf-objdata-decoded RTF \objdata at offset 0x90 1893 bytes