Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 8409eab348acd575…

MALICIOUS

RTF / .DOC

19.0 KB
MD5: dfc0f198b7b585a026e923deadac3875 SHA-1: ee49a456605ff960d4cd486bf47df2bf1476884a SHA-256: 8409eab348acd5757125f720ac43ddb77ac6544c16acaf2674d111871fc1aeb1
120 Risk Score

Malware Insights

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

The sample is an RTF document containing embedded OLE objects and triggering heuristics for the Equation Editor vulnerability. The ".objupdate" directive forces OLE activation, indicating an attempt to exploit this vulnerability for code execution. This is a common method for delivering secondary payloads, hence the high confidence in an exploitation attempt.

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_off00001212.bin
6b5d91a5b0ecf20ad0c9b269ced159301323f244d6c5955272549dbd2c202b22
rtf-objdata-decoded RTF \objdata at offset 0x1212 1387 bytes