Malicious RTF — malware analysis report

Static analysis result for SHA-256 005f18077f0642ee…

MALICIOUS

RTF

195.6 KB First seen: 2018-05-18
MD5: 2939060ea9d24fdaa3598ec00a545898 SHA-1: 47db3c7be465c06791eba250081fca446b5bfa50 SHA-256: 005f18077f0642ee450c35e5bd9d1ab8a0829d654787603b041c85d7be394dd0
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_off000006bb.bin rtf-objdata-decoded RTF \objdata at offset 0x6BB 40421 bytes
SHA-256: 5c2f6e9194d56483acf11145d5f3e4f1f0dd0f91daf0327f9100f902921b22b2