Malicious RTF — malware analysis report

Static analysis result for SHA-256 a37b10c58413b4f3…

MALICIOUS

RTF

4.2 KB
MD5: 0cac2e9112f0d3f9e816033ee9616154 SHA-1: 9aeb845d2cf013dd99c80b58496ae7e8c7ad89e8 SHA-256: a37b10c58413b4f3160b0f929935441ab0897d34b4efe6cc1a55afcee76adae5
120 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects and specifically triggers heuristics related to the Equation Editor vulnerability. The presence of \objupdate indicates an attempt to force OLE object activation, which is a common technique for exploiting this vulnerability to achieve arbitrary code execution. The file is classified as malicious, supporting the exploitation attack pattern.

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_off000000b5.bin
3f74c8a2f80b158fe9379400ef29a1a12dff734e5c9f6114610d903c93e549ff
rtf-objdata-decoded RTF \objdata at offset 0xB5 1919 bytes