Malicious RTF — malware analysis report

Static analysis result for SHA-256 06f06cb4efa4cade…

MALICIOUS

RTF

133.6 KB Created: 2017-08-25 17:38:00 First seen: 2017-08-27
MD5: 4fcbd944ba768d46991621c55a7851e9 SHA-1: bf75a737b9cb78f2b55032384b9ab0dc6248cc49 SHA-256: 06f06cb4efa4cadecfe72a44d61f1dcb9c5e84a82f9fccaef5654c61afe4ada5
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://localhost/HTA_EXPLOIT/files/hehe.pptx, indicating an attempt to download and execute a secondary payload. This is characteristic of a malicious document delivered via spearphishing.

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://localhost/HTA_EXPLOIT/files/hehe.pptx In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002c56.bin rtf-objdata-decoded RTF \objdata at offset 0x2C56 18473 bytes
SHA-256: e6d939c1940ebdd1c50b6b10917f35acbe9bc2753ddedaab66e8568156011b52

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