Malicious RTF — malware analysis report

Static analysis result for SHA-256 a70173434ba2eccf…

MALICIOUS

RTF

38.1 KB First seen: 2020-07-24
MD5: f29cb6bf36a1d5efa7da168e6a134115 SHA-1: f74121e7d08a25e8a2eb11083258c2c97e2bd61a SHA-256: a70173434ba2eccfa97cba347242d41951a100c6e898a46ecfc3b9da1685a696
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 specifically triggers the Equation Editor vulnerability, indicating exploitation for client execution. The presence of \objupdate suggests an attempt to force OLE activation, likely to trigger the exploit. Given the malicious verdict and the nature of the exploit, it is highly probable that this document is delivered via spearphishing and is intended to download and execute a secondary payload.

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_off00001636.bin rtf-objdata-decoded RTF \objdata at offset 0x1636 2132 bytes
SHA-256: d429ca13fc9499fe7c1c5a4fa1a66fa98c15b3a8251db9da661dfdf669ebd4bb

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