MALICIOUS
382
Risk Score
Malware Insights
MITRE ATT&CK
T1203 Exploitation for Client Execution
The RTF document contains embedded OLE object data and references to APIs like CreateProcess, ShellExecute, LoadLibrary, and GetProcAddress, indicating execution capabilities. The critical CVE-2017-8759 heuristic firing strongly suggests exploitation of this vulnerability. The presence of an INCLUDETEXT/INCLUDEPICTURE remote URL points to the download of a secondary payload, likely facilitated by the embedded OLE object.
Heuristics 10
-
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.
-
ClamAV: Rtf.Downloader.CVE_2017-6336326-3 critical CLAMAV_DETECTIONClamAV detected this file as malware: Rtf.Downloader.CVE_2017-6336326-3
-
Reference to CreateProcess API high SC_STR_CREATEPROCESSReference to CreateProcess API
-
Reference to ShellExecute API high SC_STR_SHELLEXECReference to ShellExecute API
-
Reference to LoadLibrary API high SC_STR_LOADLIBRARYReference to LoadLibrary API
-
Reference to GetProcAddress API high SC_STR_GETPROCADDRESSReference to GetProcAddress API
-
\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.
-
INCLUDETEXT/INCLUDEPICTURE remote URL high RTF_INCLUDE_REMOTERTF document uses INCLUDETEXT or INCLUDEPICTURE with an http:// URL — Word can fetch the remote content on open depending on Office version and external-content settings, enabling remote template injection, NTLM capture via redirects, or payload delivery
-
OLE object data medium RTF_OBJDATARTF contains 2 \objdata section(s) — embedded OLE objects
-
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://nsis.sf.net/NSIS_Error In RTF body
- http://kristinaslip1.000webhostapp.com/t.php?stats=send&thread=0In 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_off0000c568.bin |
rtf-objdata-decoded | RTF \objdata at offset 0xC568 | 2598 bytes |
SHA-256: 2cb1ad33bbdccbf6f94b7145ae8d71dd195fba677b709ebb7802f3188663d53b |
|||
objdata_01_off0000dc96.bin |
rtf-objdata-decoded | RTF \objdata at offset 0xDC96 | 2723 bytes |
SHA-256: 7322d9b1f1bae657e6a0ad1b6fb31496497e614b42e4ce47d5a19ba8537ec4e4 |
|||
Open this report in the interactive analyzer, or submit your own file for analysis.