Malicious RTF — malware analysis report

Static analysis result for SHA-256 ed43e2391788457e…

MALICIOUS

RTF

20.3 KB Created: 2016-11-27 22:42:00 First seen: 2017-11-13
MD5: 686c85e9561c5351273ebf2b9128d653 SHA-1: 676edd4520d9d14e544da68b0fb0ea2a9a9e35eb SHA-256: ed43e2391788457e5db4e4b968b02bad264371643eb0b4ef7a4e4822dc04a8ae
122 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains an OLE object that leverages CVE-2017-0199 to automatically link to and download a remote document from http://212.86.115.71/template.doc. This indicates an attempt to execute arbitrary code by exploiting a known vulnerability in Microsoft Office.

Heuristics 4

  • CVE-2017-0199 (OLE2Link / remote URL Moniker) critical CVE likely CVE_2017_0199
    RTF contains a URL Moniker OLE link whose decoded target is remote. Office can fetch and process the response through the CVE-2017-0199 OLE2Link attack path, but the server-side content type is not proven statically.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://212.86.115.71/template.doc In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00003180.bin rtf-objdata-decoded RTF \objdata at offset 0x3180 2724 bytes
SHA-256: 8f9fcf9f8345bafbf0fcadeb89e49bff394eed1004505336f8b843e88a89548f