Malicious RTF — malware analysis report

Static analysis result for SHA-256 95d4ea22169766c4…

MALICIOUS

RTF

104.3 KB Created: 2019-01-07 First seen: 2019-06-27
MD5: 72d6404e37bdc9b6838625cdfb38912f SHA-1: 9f29b48533ca41bcea40c4d72632d8055b126ad9 SHA-256: 95d4ea22169766c484f142941c9b263b759640036f7b1f920db253349bb521c3
302 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 exploit targets MSXML OLE activation and uses a remote URL moniker to fetch a secondary document, 'samaddz.doc', from 'http://192.168.1.3/samaddz.doc'. This indicates the file is designed to download and execute a further payload.

Heuristics 8

  • 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 OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • 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.1.3/samaddz.doc In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body
    • http://schemas.openxmlformats.org/drawingml/2006/mainIn RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002dc2.bin rtf-objdata-decoded RTF \objdata at offset 0x2DC2 2601 bytes
SHA-256: 93918495ba36233126101f8f1a8573ff62d0b87a845d2ccac65ff906bf7cb316
objdata_01_off00005dd3.bin rtf-objdata-decoded RTF \objdata at offset 0x5DD3 22576 bytes
SHA-256: a94625547945dd2651f81d188535bf71c9ecabb7ae50cf9af1d4ae1f98e353bc

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