Malicious RTF — malware analysis report

Static analysis result for SHA-256 d12feffef7d8b4fc…

MALICIOUS

RTF

5.1 KB First seen: 2018-11-20
MD5: 4a920d6010f9ed2028732f123226ad46 SHA-1: 35a84828e364e8223a3ec114cb7aabaaad4d4993 SHA-256: d12feffef7d8b4fc9da7a230d558ee8b8c84473673dc640b0ab46dc81f5e2721
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 that triggers the CVE-2017-8759 vulnerability. This vulnerability allows for remote code execution when the object is activated, likely leading to the download and execution of a secondary malicious payload. The presence of the \objupdate directive further ensures OLE activation.

Heuristics 3

  • SOAP Moniker — CVE-2017-8759 (SOAP WSDL RCE) critical CVE related CVE_2017_8759
    RTF \objdata decodes to OLE data containing the SOAP Moniker — CVE-2017-8759 (SOAP WSDL RCE) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
  • \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_off0000003c.bin rtf-objdata-decoded RTF \objdata at offset 0x3C 2596 bytes
SHA-256: 6bb1d45aa6d8d211b4fae4c95d65ba9d847175a24240d5422e5cbbd70d6fb86e

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