Malicious RTF — malware analysis report

Static analysis result for SHA-256 0c4ad0e29babeceb…

MALICIOUS

RTF

47.3 KB
MD5: bf242b72cd9f3ddb29c58d40b29449f9 SHA-1: a8817346e647571b31d13635b0ace6be25ef8a90 SHA-256: 0c4ad0e29babeceb69d31ae8e4c2caca74dd31837f4a92651287497ad3c510bf
120 Risk Score

Malware Insights

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

The RTF document contains OLE object data and triggers an ".objupdate" command, indicating exploitation of the Equation Editor vulnerability. This technique is commonly used to deliver a secondary payload, likely leading to arbitrary code execution on the victim's system.

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_off00000f35.bin
fe986a2a4d6714469725b557880ceb5fd38d12cf90d90200ca83d2f138866335
rtf-objdata-decoded RTF \objdata at offset 0xF35 1935 bytes