Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 6a3a0ae9f33c2e4f…

MALICIOUS

RTF / .DOC

5.66 MB Created: 2021-10-27 18:20:00
MD5: 0fe6cf79a9d6f4740feea4f1ba4a052c SHA-1: b7f6d29978db203f23ee1539ed31013b64e3065a SHA-256: 6a3a0ae9f33c2e4fe21e5096a6d27cc0148ef48bf40fe6de4af19f6b0f5e2da0
362 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple critical heuristic firings indicating exploitation of CVE-2017-8570, CVE-2017-8759, and CVE-2026-21514. These vulnerabilities are known to allow for arbitrary code execution, likely to download and run a secondary payload. The presence of OLE object data and excessive hex data further supports the payload delivery mechanism.

Heuristics 10

  • 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-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759
    RTF 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 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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1651KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 3 \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

Extracted artifacts 4

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00540dff.bin
85489890c7d69f1b9c243ea139921db11e4584c5f67c89522e1b4e5a4ccba0af		 rtf-objdata-decoded RTF \objdata at offset 0x540DFF 116592 bytes
objdata_01_off0057c1ee.bin
79fc97ccaa38d91458cde2c6b1b01259c64ac0c6d61e1a01b0a66bc01e3e6a8d		 rtf-objdata-decoded RTF \objdata at offset 0x57C1EE 2632 bytes
objdata_02_off0057d791.bin
44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037		 rtf-objdata-decoded RTF \objdata at offset 0x57D791 12297 bytes
rtf_svb_00004896.zip
24a53a09dd578ae9726b4a2c5f1f2f62fcce17cc0dd17d3ba3b092212bc43d09		 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.