Malicious RTF / .DOC — malware analysis report

Heuristics 11

• Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570
  RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) 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 / CVE-2017-8759 (OLE2Link auto-activated remote loader) critical CVE related RTF_OLE2LINK_REMOTE_MONIKER_LOADER
  RTF embeds an OLE2Link object that is force-activated with \objupdate (no user interaction on open) and fetches a remote second stage — through an INCLUDETEXT/INCLUDEPICTURE field or the OLE object's own moniker. This is the OLE2Link auto-update attack path shared by CVE-2017-0199 (server returns an HTA/scriptlet) and CVE-2017-8759 (server returns a SOAP WSDL the .NET parser compiles). Office processes the fetched response through the same code path; the specific CVE depends on the now-unreachable server content type.
• Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED
  RTF 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_21514
  RTF 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.
• Automatically linked OLE object high RTF_OBJAUTLINK
  RTF 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_OBJUPDATE
  RTF contains \objupdate — forces automatic OLE object instantiation when the document is opened, bypassing user interaction. Almost exclusively seen in Equation Editor exploit documents.
• \objupdate activation with payload hidden outside \objdata high RTF_OBJUPDATE_LOOSE_HEX_PAYLOAD
  RTF declares an OLE object with \objupdate (forces automatic activation when the document opens) but has no \objdata destination; the object payload is instead dumped as a large loose hex-encoded region in the document body. This split hides the payload from \objdata-scoped parsers while Word still instantiates the object. Structurally exclusive to weaponised documents.
• Suspicious extracted artifact high EXTRACTED_FILE_STATIC_TRIAGE
  One 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.
• OLE object data medium RTF_OBJDATA
  RTF contains 4 \objdata section(s) — embedded OLE objects
• Embedded OLE object medium RTF_OBJEMB
  RTF contains \objemb — embedded OLE object
• Embedded URL info EMBEDDED_URL
  One 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 In RTF body

Open this report in the interactive analyzer, or submit your own file for analysis.