Malicious RTF — malware analysis report

Static analysis result for SHA-256 cbc8ef751c517241…

MALICIOUS

RTF

4.3 KB
MD5: e6c04a3b4a271d0b6e5080054b401601 SHA-1: d597e8470cb5781eb8e40bef3b893124563ff882 SHA-256: cbc8ef751c517241a50ea5205624152631b6864c3ce8488f01a8fc373a953aaa
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 execute a secondary payload, making it a likely initial vector for a broader attack.

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_off0000003e.bin
b3893d990377d24bfe4f6201cdc218f05c060624030710413baa9862ad8fbfe1
rtf-objdata-decoded RTF \objdata at offset 0x3E 2183 bytes