Malicious RTF — malware analysis report

Static analysis result for SHA-256 ab0ff4baf19c343d…

MALICIOUS

RTF

44.3 KB Created: 2017-09-11 03:41:00 First seen: 2017-09-14
MD5: 18cda6ee7ad8dd8401d070b25258c311 SHA-1: e83908c5c1639cb86309ed691c0cc0c6ff795400 SHA-256: ab0ff4baf19c343dbdb3ce951b9a92f6a6e7fcdddd68e5142b50818ab207d1a6
182 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. This vulnerability allows the file to automatically link to and download a remote resource from the URL http://192.168.56.103/test.rtf. The embedded OLE object suggests an attempt to execute a secondary payload, likely downloaded from the specified URL.

Heuristics 5

  • 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.
  • ClamAV: Rtf.Exploit.CVE_2017_0199-6335035-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Exploit.CVE_2017_0199-6335035-0
  • 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://192.168.56.103/test.rtf 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_off00002c10.bin rtf-objdata-decoded RTF \objdata at offset 0x2C10 2601 bytes
SHA-256: 84d1e71444c349d38dce33ce146689827c9f47dd31e65569655f903cda968ee1

Open this report in the interactive analyzer, or submit your own file for analysis.