Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 e2ea7ad7bb5d55e0…

MALICIOUS

RTF / .DOC

1.02 MB First seen: 2026-05-25
MD5: db5535e87487ddee9e21296d8f968800 SHA-1: cdb3649ddf5b7ef07ec63483a7012d505618e6dc SHA-256: e2ea7ad7bb5d55e074c8a9d81f3399841c136ffbaa95e2172637a0047b4cc931
380 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution: Malicious File T1566.001 Phishing: Spearphishing Attachment T1027 Obfuscated Files or Information T1137.003 Software Deployment Tools: Windows Management Instrumentation

The RTF document contains multiple OLE objects, including automatically linked and updated objects, which are designed to execute embedded content. High severity heuristics indicate excessive hex data within these objects, suggesting a hidden payload. The presence of a macro/content-enable lure further supports the intent to trick the user into activating the malicious content, likely leading to the download and execution of a second-stage payload.

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-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.
  • 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 ~1037KB of hex-encoded data inside \objdata sections — may hide a payload
  • 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
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
🗂 Part of campaign: shared payload 51ef705eef 49 samples

Related samples 8

Ranked by shared artifacts, heuristics, extracted URLs, CVEs, and signatures.

Full JSON: related samples API

Extracted artifacts 4

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000bb2.bin rtf-objdata-decoded RTF \objdata at offset 0xBB2 408296 bytes
SHA-256: 4ff8db8c127d3d211a7ba885cca68d0862b10092a8a79c1767222ac295ed2002
objdata_01_off00007361.bin rtf-objdata-decoded RTF \objdata at offset 0x7361 408269 bytes
SHA-256: 026defd18704019c70c39854424774167369985696febe504b1c023905c27c61
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): WScript.Shell"")")
objdata_02_off000d6932.bin rtf-objdata-decoded RTF \objdata at offset 0xD6932 2632 bytes
SHA-256: 51ef705eef602ac6eb91c2063c8f50d4e54b5e051b60429031d41133bc7df645
objdata_03_off000d7ed5.bin rtf-objdata-decoded RTF \objdata at offset 0xD7ED5 12297 bytes
SHA-256: e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7

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