Malicious RTF — malware analysis report

Static analysis result for SHA-256 f0622e5eaaa2c761…

MALICIOUS

RTF

45.5 KB Created: 2017-11-16 01:20:00 First seen: 2017-11-20
MD5: 7012c4e0183151b7f90b283869f41175 SHA-1: baa6c410b2473f13a1e0572faff9f8387bc1eff6 SHA-256: f0622e5eaaa2c761ad3ad0d626e9b84bc8ce40779ee5af852b31f2d2572a6fb0
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 is automatically linked and exploits CVE-2017-0199. This vulnerability allows the file to download a secondary document from the URL http://eatongroup.us/SD/p.doc, which is likely a malicious payload. The presence of the OLE object and the specific CVE exploit strongly indicate a malicious intent to execute remote code.

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://eatongroup.us/SD/p.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_off000033f8.bin rtf-objdata-decoded RTF \objdata at offset 0x33F8 3640 bytes
SHA-256: 3e799cbc1c9e58216dee7bc03b0761777de922f899b7429fc61e7e4718e62e34