MALICIOUS
262
Risk Score
Malware Insights
MITRE ATT&CK
T1204.002 Malicious File: User Execution
T1566.001 Phishing: Spearphishing Attachment
The RTF file contains multiple indicators of malicious OLE object embedding, including excessive hex data and automatic linking. Crucially, the critical heuristic firing for CVE-2017-8759 indicates exploitation of MSXML SAX. This suggests the file is designed to exploit this vulnerability, likely to download and execute a secondary payload. The presence of embedded OLE objects and the specific CVE targeted point towards a malicious document designed for exploitation.
Heuristics 8
-
CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759RTF 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.
-
Composite Moniker in RTF OLE object high RTF_COMPOSITE_MONIKER_RELATEDRTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
-
Automatically linked OLE object high RTF_OBJAUTLINKRTF 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_OBJUPDATERTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
-
Large hex data blocks in OLE object high RTF_EXCESSIVE_HEXRTF contains ~1002KB of hex-encoded data inside \objdata sections — may hide a payload
-
OLE object data medium RTF_OBJDATARTF contains 3 \objdata section(s) — embedded OLE objects
-
Embedded OLE object medium RTF_OBJEMBRTF contains \objemb — embedded OLE object
-
Embedded URL info EMBEDDED_URLOne 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://schemas.microsoft.com/office/word/2003/wordml
Extracted artifacts 3
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
objdata_00_off000b2451.binf49f03575026d1f98b7e0eb44b5325f14e7033c0b64822159b2a47d9bd2b6e62 |
rtf-objdata-decoded | RTF \objdata at offset 0xB2451 | 59037 bytes |
objdata_01_off000d049e.bin9d9bc825f2fa5e0ed8db7dce6823e199ad9c775873472d42887214589f205470 |
rtf-objdata-decoded | RTF \objdata at offset 0xD049E | 2632 bytes |
objdata_02_off000d1a41.bin44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037 |
rtf-objdata-decoded | RTF \objdata at offset 0xD1A41 | 12297 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.