MALICIOUS
302
Risk Score
Malware Insights
MITRE ATT&CK
T1203 Exploitation for Client Execution
T1566.001 Spearphishing Attachment
The RTF file contains critical heuristics indicating exploitation of CVE-2017-0199, which is known to leverage remote URL monikers to download and execute arbitrary content. The embedded URL http://192.168.56.103/test.rtf is highly suspicious and likely points to the secondary payload. The presence of OLE object data and automatic linking further supports the exploitation vector.
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.
-
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.Exploit.CVE_2017_0199-6335035-0 critical CLAMAV_DETECTIONClamAV detected this file as malware: Rtf.Exploit.CVE_2017_0199-6335035-0
-
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.
-
OLE object data medium RTF_OBJDATARTF contains 3 \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://192.168.56.103/test.rtf In RTF body
- http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body
Extracted artifacts 3
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
objdata_00_off00002d72.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x2D72 | 2601 bytes |
SHA-256: 6d84b3b3e5e333f72d242b92a014a2462b9fedc8d8bd269ba63c6595aa3bc207 |
|||
objdata_01_off000063ba.bin |
rtf-objdata-decoded | RTF \objdata at offset 0x63BA | 5432 bytes |
SHA-256: 1f7b93353f542b96cc60be3139228db5521fc97a3ecf7ec6c210e83998bf2d36 |
|||
objdata_02_off0000ab8c.bin |
rtf-objdata-decoded | RTF \objdata at offset 0xAB8C | 6968 bytes |
SHA-256: 6e4994d9120c15bbff11652deaf486f5cb96cca89b378455c73ad2fbf45bdc24 |
|||
Open this report in the interactive analyzer, or submit your own file for analysis.