Malicious RTF — malware analysis report

Static analysis result for SHA-256 aa9c4b64b3081a8f…

MALICIOUS

RTF

51.5 KB Created: 2017-11-12 07:19:00 First seen: 2017-11-20
MD5: 4c461259bcc5b7799db2b802b570447b SHA-1: 264b6a45399471b45e6eb1087b1086247ed75c18 SHA-256: aa9c4b64b3081a8f15413ffc55a331e3bf2fc46b43dd372a28df48e0774649e8
282 Risk Score

Malware Insights

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

The RTF file exploits CVE-2017-0199 by leveraging a remote URL moniker to fetch and execute a secondary RTF document from http://107.167.10.47/Doc1.rtf. The presence of OLE object data and automatic linking further indicates malicious intent, likely to deliver a further stage payload.

Heuristics 7

  • 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.
  • \objupdate forces OLE activation high RTF_OBJUPDATE
    RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \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://107.167.10.47/Doc1.rtf In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002a2e.bin rtf-objdata-decoded RTF \objdata at offset 0x2A2E 2601 bytes
SHA-256: 2cd6dcf0ef49599086cab6208859b89e05a1a46947015e1f906401cbb984046a
objdata_01_off0000540b.bin rtf-objdata-decoded RTF \objdata at offset 0x540B 2601 bytes
SHA-256: eefab45d42fefc00c498c2ebf5cbec6240a4035c2a4179a504e1581f745f5c8a

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