Malicious RTF — malware analysis report

Static analysis result for SHA-256 62e8b910dcdc199f…

MALICIOUS

RTF

50.7 KB Created: 2017-04-16 23:44:00 First seen: 2017-10-10
MD5: c155624255e90a9d7f55f7af285fed30 SHA-1: f134c7319f797e10a7d8bb32f258b48eda97bc57 SHA-256: 62e8b910dcdc199f7fe7a064b2f914a1440cc8c344be58c086e939a8c987f62a
282 Risk Score

Malware Insights

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

The RTF file contains an OLE object that is automatically linked and updated, triggering an exploit for CVE-2017-0199. This exploit is designed to download and execute a payload from the embedded URL http://80.82.67.42/test.hta, indicating a downloader or initial access mechanism.

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 / weaponized URL) critical CVE exact CVE_2017_0199_WEAPONIZED_URL
    RTF contains a URL Moniker OLE link to a script/HTA/template-style remote loader, matching the tighter static CVE-2017-0199 shape.
  • 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 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://80.82.67.42/test.hta 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_off00001f1e.bin rtf-objdata-decoded RTF \objdata at offset 0x1F1E 3924 bytes
SHA-256: 4c3f9ed5e72162fb9171909215dd98db89ef1a90033e402824194d7021003516

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