MALICIOUS
302
Risk Score
Malware Insights
MITRE ATT&CK
T1203 Exploitation for Client Execution
The RTF file contains multiple critical heuristic firings indicating exploitation of CVE-2017-0199 and CVE-2017-8759. These vulnerabilities are leveraged to download a secondary payload from the URL http://izmirspotum.com/wp-content/t.php?thread=0&t=h. The presence of large amounts of hex-encoded data within OLE objects further suggests the embedding of a malicious payload.
Heuristics 8
-
SOAP Moniker — CVE-2017-8759 (SOAP WSDL RCE) critical CVE_2017_8759RTF \objdata decodes to OLE data containing the SOAP Moniker — CVE-2017-8759 (SOAP WSDL RCE) 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-0199 (OLE2Link / remote URL Moniker) critical CVE likely CVE_2017_0199RTF 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.Downloader.CVE_2017-6336326-3 critical CLAMAV_DETECTIONClamAV detected this file as malware: Rtf.Downloader.CVE_2017-6336326-3
-
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.
-
Large hex data blocks in OLE object high RTF_EXCESSIVE_HEXRTF contains ~2811KB of hex-encoded data inside \objdata sections — may hide a payload
-
OLE object data medium RTF_OBJDATARTF contains 2 \objdata section(s) — embedded OLE objects
-
OlePres presentation stream in RTF OLE object medium RTF_OLEPRES_STREAMRTF contains an embedded OLE object with an OlePres presentation stream. OlePres is an OLE presentation marker and is not enough on its own to identify CVE-2025-21298.
-
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://izmirspotum.com/wp-content/t.php?stats=send&thread=0 In RTF body
- http://izmirspotum.com/wp-content/t.php?thread=0&t=hIn RTF body
- http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body
Extracted artifacts 2
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
objdata_00_off00002a32.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x2A32 | 4666 bytes |
SHA-256: 8a52bcf52ba044e5b98e359615412322772d8c248c1cc34d4913d74598309520 |
|||
objdata_01_off00005259.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x5259 | 4372 bytes |
SHA-256: 7d83a8e98f989a65cbc997285a257f31882707b71875110cee49c9f405295f5b |
|||
Open this report in the interactive analyzer, or submit your own file for analysis.