Malicious RTF — malware analysis report

Static analysis result for SHA-256 51d9f637f3794f9e…

MALICIOUS

RTF

168.2 KB First seen: 2018-05-18
MD5: c452882aac6a8f34d403ad11dd3eebbb SHA-1: d5cd12939c56ba64ab581d8dbd587eca666d23c8 SHA-256: 51d9f637f3794f9e76da3105dfb8ac3b7f2cccd1621002c15f502a3914e3c3e8
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 triggers the CVE-2017-8759 vulnerability using a SOAP Moniker. This indicates the file is designed to exploit a known SOAP WSDL Remote Code Execution vulnerability to download and execute a secondary payload. The ".objupdate" directive further forces OLE object activation, confirming the exploitation attempt.

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_off000006bc.bin rtf-objdata-decoded RTF \objdata at offset 0x6BC 31654 bytes
SHA-256: 42047473b551cf0d5c3607704679d45516900f83026fec10bc00cc30eb37d778