Malicious RTF — malware analysis report

Static analysis result for SHA-256 a3c7c7aef16f9626…

MALICIOUS

RTF

5.17 MB Created: 2025-09-16 18:10:00 First seen: 2025-11-03
MD5: 602c78fe670d552d120ce5e1f510be92 SHA-1: b7803ce28609c9740029b3985d7e0e068d8a00c4 SHA-256: a3c7c7aef16f962654091a2249d19f1d863aa9d90f3c63c716b445d0f67b5236
422 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains multiple critical heuristic firings indicating exploitation of CVE-2017-11882 (Equation Editor) and CVE-2017-8759 (MSXML SAX OLE activation). The presence of large hex-encoded data blocks and a PE header within the OLE object suggests the embedding of a malicious payload. The document body content appears to be benign calendar data, indicating the lure is likely within the embedded OLE objects.

Heuristics 11

  • 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.
  • Equation Editor activation — CVE-2017-11882 related high CVE related CVE_2017_11882_ACTIVATION_RELATED
    RTF decodes to an Equation.3 ProgID and requests OLE activation with \objemb plus \objupdate. This reaches the legacy Equation Editor attack surface used by CVE-2017-11882/CVE-2018-0802 documents, but the malformed MTEF/native payload needed for stronger attribution was not recovered.
  • 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.
  • Split hex Equation Editor ProgID + OLE object critical RTF_EQUATION_EDITOR
    RTF embeds the Equation.3 ProgID as hex bytes near OLE object activation and splits the byte stream with whitespace or an ignorable RTF group. This is an Equation Editor OLE activation surface commonly used by CVE-2017-11882 / CVE-2018-0802 exploit documents.
  • PE header (with DOS stub) in hex data critical RTF_MZ_HEX
    Hex-encoded PE (MZ + DOS stub) found inside RTF — likely an embedded executable payload
  • \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 ~1840KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \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://www.pdf-tools.com\
    • http://ocsp.verisign.com0
    • http://schemas.microsoft.com/office/word/2003/wordml
    • http://www.adobe.com/go/security-and-compliance
    • https://acrobat.adobe.com/us/en/
    • http://www.pdf-tools.com
    • http://www.w3.org/1999/02/22-rdf-syntax-ns#
    • http://purl.org/dc/elements/1.1/
    • http://ns.adobe.com/xap/1.0/
    • http://ns.adobe.com/xap/1.0/mm/
    • http://ns.adobe.com/xap/1.0/sType/ResourceRef#
    • http://ns.adobe.com/xap/1.0/sType/ResourceEvent#
    • http://ns.adobe.com/pdf/1.3/
    • https://www.verisign.com/rpa
    • http://csc3-2010-crl.verisign.com/CSC3-2010.crl0D
    • https://www.verisign.com/rpa0
    • http://csc3-2010-aia.verisign.com/CSC3-2010.cer0
    • https://www.verisign.com/cps0*
    • http://logo.verisign.com/vslogo.gif04
    • http://crl.verisign.com/pca3-g5.crl04
    • https://www.globalsign.com/repository/0
    • http://ocsp.globalsign.com/ca/gstsacasha384g40C
    • http://secure.globalsign.com/cacert/gstsacasha384g4.crt0
    • http://crl.globalsign.com/ca/gstsacasha384g4.crl0
    • http://ocsp2.globalsign.com/rootr606
    • http://crl.globalsign.com/root-r6.crl0G

Extracted artifacts 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000af73f.bin
3d901554cd27ff3b6d1d240d21e90a3b575ec0f605decab81741443e9515fa90		 rtf-objdata-decoded RTF \objdata at offset 0xAF73F 816362 bytes
objdata_01_off0024986f.bin
24ee741dd41bc27803d80f81b66eba686fe8f5d17bd847727dc5d94834bd3188		 rtf-objdata-decoded RTF \objdata at offset 0x24986F 584826 bytes
rtf_svb_00000009.zip
2352c9fffd0fd8eba341b4fd80ae0a94a85929bec042e2061b1f17cd52df50f2		 rtf-svb-package RTF \svb hex-decoded ZIP at offset 0x9 116884 bytes

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