MALICIOUS
282
Risk Score
Malware Insights
MITRE ATT&CK
T1204.002 Malicious File
T1559.001 Component Object Model
The RTF document contains multiple OLE objects and triggers the ".objupdate" directive, indicating an attempt to activate embedded content. High-severity heuristics identify exploitation of CVE-2017-8759 and CVE-2026-21514, suggesting the document is designed to execute a malicious payload upon opening. The presence of large hex data blocks within OLE objects further supports the hiding of a payload. No scripts were extracted, but the exploit vectors are clear.
Heuristics 9
-
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.
-
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.
-
CVE-2026-21514 — Word/OLE security bypass in RTF high CVE likely CVE_2026_21514RTF contains a hidden \svb hex package with DrsE2oDoc and downRevStg drawing compatibility parts. This matches an observed CVE-2026-21514 exploitation shape that manipulates Word's internal document structure and trust decisions.
-
\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 ~1651KB of hex-encoded data inside \objdata sections — may hide a payload
-
OLE object data medium RTF_OBJDATARTF contains 3 \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.microsoft.com/office/word/2003/wordml}}\paperw12240\paperh15840\margl1440\margr1440\margt1440\margb1440\gutter0\ltrsect
Extracted artifacts 4
Files carved from inside the sample during analysis.
| Filename | Kind | Source | Size |
|---|---|---|---|
objdata_00_off00540dff.bin86d485c56bbd83c0f33f39ef78c16fbb327bc33db98fe36a5185c8c255be4272 |
rtf-objdata-decoded | RTF \objdata at offset 0x540DFF | 96097 bytes |
|
Detection
ClamAV:
No threats found
Obfuscation or payload:
likely
Carved artifact contains 1 shell/COM execution token(s).
|
|||
objdata_01_off00571b66.binad7bf1923f855fca5949d0c557a2a819b106cd84b204870bcc59064eb0c6e331 |
rtf-objdata-decoded | RTF \objdata at offset 0x571B66 | 2632 bytes |
objdata_02_off00573109.bin44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037 |
rtf-objdata-decoded | RTF \objdata at offset 0x573109 | 12297 bytes |
rtf_svb_00004896.zip24a53a09dd578ae9726b4a2c5f1f2f62fcce17cc0dd17d3ba3b092212bc43d09 |
rtf-svb-package | RTF \svb hex-decoded ZIP at offset 0x4896 | 819490 bytes |
Open this report in the interactive analyzer, or submit your own file for analysis.