MALICIOUS
302
Risk Score
Malware Insights
MITRE ATT&CK
T1204 Malicious Link
T1204.002 Malicious Link: Malicious File
T1059 Command and Scripting Interpreter
T1566 Phishing
T1566.001 Phishing: Spearphishing Attachment
The RTF document contains multiple indicators of exploitation for CVE-2017-8570 and CVE-2017-8759, which are known to facilitate the execution of malicious scripts via OLE object activation. The presence of large, hex-encoded data blocks within OLE objects strongly suggests the embedding of a payload. The document body itself appears to be a benign-looking invoice, likely serving as a lure.
Heuristics 9
-
Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE_2017_8570RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
-
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.
-
\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 ~1023KB 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
-
Suspicious extracted artifact medium EXTRACTED_FILE_STATIC_TRIAGEOne or more files extracted from inside this sample matched static suspicious-content checks such as script obfuscation, encoded payload blobs, packed data, or execution/download terms.
-
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_off000d5dd1.bin51c9074e213a0c1d17f7c0397318b2a638aefd67b8d75f12d61249fdabdee23a |
rtf-objdata-decoded | RTF \objdata at offset 0xD5DD1 | 34287 bytes |
|
Detection
ClamAV:
No threats found
Obfuscation or payload:
likely
Carved artifact contains 1 shell/COM execution token(s).
|
|||
objdata_01_off000e7503.bin24fedef2d4fe5e3d6666fae2543850c54134511ad6be8583d5aa0438ef699c5d |
rtf-objdata-decoded | RTF \objdata at offset 0xE7503 | 2632 bytes |
objdata_02_off000e8aa6.bin142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78 |
rtf-objdata-decoded | RTF \objdata at offset 0xE8AA6 | 12297 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.