Malicious RTF — malware analysis report

Static analysis result for SHA-256 6321dbbc44db6b79…

MALICIOUS

RTF

52.8 KB Created: 2019-01-06 23:23:00 First seen: 2019-05-16
MD5: b58cf57a0e51712b6ae9d231ac903598 SHA-1: 0297eb84ec89613617298362dbb19f6c7587ff2d SHA-256: 6321dbbc44db6b79e9301dfa29cad725d63d7d4b44a8dc98f82f2c1598de76ad
282 Risk Score

Malware Insights

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

The RTF file contains critical vulnerabilities, specifically CVE-2017-0199 and CVE-2017-8759, which are exploited for client execution. The file attempts to download a secondary payload from the URL http://192.168.1.3/samaddz.doc, indicating a downloader or dropper functionality. The presence of OLE object data and automatic linking further supports the exploitation vector.

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 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://192.168.1.3/samaddz.doc In RTF body
    • http://schemas.microsoft.com/office/word/2003/worIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002d0c.bin rtf-objdata-decoded RTF \objdata at offset 0x2D0C 2601 bytes
SHA-256: 9b897b8381d77dd25a6e44f32b1ae56fe7249b08c012b30d6cc45cbcca1e9831

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