Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 74f608489eaa6b17…

MALICIOUS

RTF / .DOC

27.2 KB
MD5: f29a5b0872f283c80510a4f506d60847 SHA-1: e2613eb0baaeefe8e6c64dcbfac814d492f10f97 SHA-256: 74f608489eaa6b17de0cda5f7cda89b714fcf7705c3866224a06334550bb2fb3
120 Risk Score

Malware Insights

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

The sample is an RTF document that contains embedded OLE objects and triggers the ".objupdate" directive, indicative of an exploit targeting the Equation Editor vulnerability. This technique is commonly used to achieve arbitrary code execution, likely for downloading and executing a second-stage payload. The specific exploit used is identified by the RTF_EQUATION_EDITOR heuristic.

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_off00001bd7.bin
0255feadf72b688c22335712e2d1d5e3ca55c9d3425fd33a9564c55f8e729366
rtf-objdata-decoded RTF \objdata at offset 0x1BD7 1610 bytes