Malicious RTF — malware analysis report

Static analysis result for SHA-256 9c2c6960e6112bf7…

MALICIOUS

RTF

18.0 KB First seen: 2020-07-24
MD5: 6946025d80f9ff3a7367fd7f40d3b30a SHA-1: 5c37f1b025f2bf77806ded97d0545c3331a01569 SHA-256: 9c2c6960e6112bf7a9a8bc67cea25b45be53ca71f4d39d538bccf62ff981822f
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. While no specific payload or C2 infrastructure was directly extracted, the technique strongly suggests the file is a dropper intended to download and execute a secondary stage malicious 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_off00000b14.bin rtf-objdata-decoded RTF \objdata at offset 0xB14 2002 bytes
SHA-256: 96bf09b4c74e85af604a5b878495eef276d7526818a0f45b6dde61b89760aeb6