MALICIOUS
200
Risk Score
Malware Insights
MITRE ATT&CK
T1204.002 Malicious File: User Execution
T1559.001 Component Object Model Hijacking
The sample is an RTF document that contains an embedded OLE object, specifically triggering heuristics for Equation Editor and CVE-2017-8759. The ".objupdate" heuristic indicates that the embedded object is designed to be activated automatically upon opening the document, likely leading to the execution of malicious code. The presence of these critical heuristics strongly suggests an exploit targeting the Equation Editor vulnerability.
Heuristics 6
-
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.
-
Equation Editor CLSID critical RTF_EQUATION_EDITOREquation Editor OLE CLSID found inside an OLE object — exploited by CVE-2017-11882 / CVE-2018-0802 / CVE-2018-0798
-
\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 1 \objdata section(s) — embedded OLE objects
-
Embedded OLE object medium RTF_OBJEMBRTF contains \objemb — embedded OLE object
-
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 1
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
objdata_00_off001389e2.bin6d7baafde49b3791acd5f9cd040a5671a53549674753a0acbab6643966babe4e |
rtf-objdata-decoded | RTF \objdata at offset 0x1389E2 | 3739 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.