MALICIOUS
242
Risk Score
Malware Insights
MITRE ATT&CK
T1203 Exploitation for Client Execution
T1566.001 Spearphishing Attachment
The RTF file contains multiple indicators of malicious activity, including the presence of OLE objects and a Composite Moniker, strongly suggesting exploitation of CVE-2017-8570. This vulnerability is known to drop and execute SCT scripts. The heuristic 'CVE_2017_8570' specifically points to this exploit, which facilitates client execution by dropping a script. The presence of a large, hex-encoded OLE object further supports the likelihood of a hidden payload.
Heuristics 8
-
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.
-
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 ~1200KB of hex-encoded data inside \objdata sections — may hide a payload
-
OLE object data medium RTF_OBJDATARTF contains 7 \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.openxmlformats.org/drawingml/2006/main In RTF body
Extracted artifacts 7
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
objdata_00_off00000025.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x25 | 205 bytes |
SHA-256: 75a725fc96463ea024899f12597b26031b1a5d84ddd2de407d47914073b3db59 |
|||
objdata_01_off000001ee.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x1EE | 600403 bytes |
SHA-256: 1171205b7cf49db6a74e4c2f209d05f921c161ba7fb5c5a85395929b7806dd30 |
|||
|
Detection
ClamAV:
No threats found
Obfuscation or payload:
likely
Static shellcode analysis found candidate code region(s). Indicators: NOP sled
|
|||
objdata_02_off001a9855.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x1A9855 | 1068 bytes |
SHA-256: 2b28d78ceb2a564ae30f2b6865926b068f3f920a373c2e3fc4cb865091eddd89 |
|||
objdata_03_off001aa0e6.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x1AA0E6 | 84172 bytes |
SHA-256: 0d3775908ff9633231ed31366d571cc52d59ead61d5d35f29339e92b5565ca38 |
|||
objdata_04_off001d32b6.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x1D32B6 | 369 bytes |
SHA-256: 3c0b4878e98d51d984a06b9ba36e54869ecd67e41f335730fced4ca28976d877 |
|||
objdata_05_off001d35d4.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x1D35D4 | 890 bytes |
SHA-256: 21dcdf875b1972c61c0e8c2c2123f9a95c8f29fb4a2cf8bf52511b328881de8e |
|||
objdata_06_off001d3d46.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x1D3D46 | 2633 bytes |
SHA-256: 27c6d10cfe7974ebf40c1200cc005f9878cc37b7d49ece9cbc396d700c38918a |
|||
Open this report in the interactive analyzer, or submit your own file for analysis.