Malicious RTF — malware analysis report

Static analysis result for SHA-256 e6b4add8fa00c6d8…

MALICIOUS

RTF

45.5 KB Created: 2017-11-20 12:15:00 First seen: 2017-11-29
MD5: 6a3f0d6f131852ac25e3784cdebb1435 SHA-1: 44f4e6eb4d87d56b8cec1aca6a11b96de35728e5 SHA-256: e6b4add8fa00c6d871248172d2a12fce550b2548e30336967cd9a1dbfeb2d1d2
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 exploits CVE-2017-0199, a known vulnerability for remote code execution. This exploit is designed to download a secondary payload from the URL http://http//test.com/1.jpg. The presence of the OLE object and the specific CVE firing strongly indicate a malicious document intended to deliver further malware.

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://http//test.com/1.jpg 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_off000033ec.bin rtf-objdata-decoded RTF \objdata at offset 0x33EC 3640 bytes
SHA-256: 9b0098c2052c294035dd1e4895a93e9b9872d3a234fca0d5a717d01026c3d22e