Malicious RTF — malware analysis report

Static analysis result for SHA-256 08294bb757d0828e…

MALICIOUS

RTF

47.2 KB Created: 2017-09-23 12:28:00 First seen: 2017-10-10
MD5: b960d33e31fccc28f1835420983fb089 SHA-1: 3d3fa0eace9bf287e57a395c1e52402e2ae8eedc SHA-256: 08294bb757d0828e52ac899db10a3b8653c1bcf52aeb3cfcf31edcd41f379ebb
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, a known vulnerability for remote code execution. The exploit targets the URL http://192.168.0.134/ms/ms.rtf, which likely serves a secondary malicious payload. This indicates a spearphishing attachment attack vector designed to download and execute further malware.

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.0.134/ms/ms.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_off0000288b.bin rtf-objdata-decoded RTF \objdata at offset 0x288B 2601 bytes
SHA-256: 1d985617a22760b5558c7600037f819f3d60ee7fa559da2597e25dd90532df35