Malicious RTF — malware analysis report

Static analysis result for SHA-256 745432050ad32513…

MALICIOUS

RTF

11.8 KB
MD5: 2dac76c2315c49868fc1c115f9cc4f7f SHA-1: 92b7be8d4179c1037d367e5a0957e02bb2bdab67 SHA-256: 745432050ad32513f9bfefee18a6b6421770f63e56f1d1dd58ec96c48f6d23d5
120 Risk Score

Malware Insights

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

The RTF file contains an embedded OLE object with a split Equation Editor ProgID, indicating exploitation of a known vulnerability (CVE-2017-11882). The \objupdate directive forces the activation of this object, which is designed to execute arbitrary code. This technique is commonly used to download and run a second-stage payload, making the initial document a delivery mechanism for further malicious activity.

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 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001787.bin
d7c615d805eadab22eb74b3eeb11791289b22aca201d14e6e613f7582e9f46e1
rtf-objdata-decoded RTF \objdata at offset 0x1787 2187 bytes