Malicious RTF — malware analysis report

Static analysis result for SHA-256 8bc27262dca0ee90…

MALICIOUS

RTF

3.2 KB First seen: 2019-09-30
MD5: 49e061d6a8d3bba8d69b905710d6ce4e SHA-1: 64bd1ee15228c7e16c7b4bf5da329865a2cb033a SHA-256: 8bc27262dca0ee90634a94423dfe24d09101e3acce256b4f70e58bdf19668d7a
120 Risk Score

Malware Insights

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

The RTF file contains critical heuristics indicating the exploitation of the Equation Editor vulnerability (CVE-2017-11882). The presence of OLE object data and the \objupdate directive strongly suggest that the file is designed to trigger code execution upon opening. This is a common technique for delivering secondary malware payloads.

Heuristics 3

  • Split hex Equation Editor ProgID + OLE object critical CVE likely 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_off0000003b.bin rtf-objdata-decoded RTF \objdata at offset 0x3B 1594 bytes
SHA-256: cebdd3be3b642edc4273b22295506460c09a8d2b4a665ffd1ccd80c98c2c4f40

Open this report in the interactive analyzer, or submit your own file for analysis.