Malicious RTF — malware analysis report

Static analysis result for SHA-256 ff898a8a9f3a09c5…

MALICIOUS

RTF

189.5 KB Created: 2017-08-25 18:00:00 First seen: 2017-08-27
MD5: 2c6f816e5dd343ac7b61d49257bd126d SHA-1: de9ad6dd84946d2e4308e423cdb3c517e7c35b10 SHA-256: ff898a8a9f3a09c519818cbfb38d34b19e9482bb7dc4610f8225bd2475c327a5
304 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple high and critical severity heuristics indicating exploitation of CVE-2017-0199 and CVE-2017-8759. The embedded URL 'http://localhost/HTA_EXPLOIT/files/alg1.png' is likely the source of a secondary payload. The document body contains only random characters, suggesting it is not intended for user interaction but rather to host the exploit.

Heuristics 9

  • CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
  • 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.
  • Package object class high RTF_OBJCLASS_PACKAGE
    OLE Package object — can wrap arbitrary files
  • OLE object data medium RTF_OBJDATA
    RTF contains 3 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Suspicious extracted artifact info EXTRACTED_FILE_STATIC_TRIAGE
    One or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
  • 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/alg1.png In RTF body
    • http://schemas.microsoft.com/office/word/20In RTF body

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002e4a.bin rtf-objdata-decoded RTF \objdata at offset 0x2E4A 60623 bytes
SHA-256: 81891adeb2b8d8127094b6bf292fa9368607437a7bdd4fa84c79375dfef3f2f4
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.86, consistent with packed or encrypted content.
objdata_01_off000261e3.bin rtf-objdata-decoded RTF \objdata at offset 0x261E3 3714 bytes
SHA-256: be7912d4323fff24dfc7fb7c06edab0061a98432499ddae3bd1d54693113c845
objdata_02_off0002830d.bin rtf-objdata-decoded RTF \objdata at offset 0x2830D 3714 bytes
SHA-256: 89a8b39a05bea173060f558abe16edb3e4ca9a1419db45fe603d4faaa59b4e3a

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