RTF / .DOC malware analysis — malicious · 4caa64908b36893b

MALICIOUS

RTF / .DOC

3.78 MB

MD5: 95f8e935279c289154b784d37bfdbae7 SHA-1: 3e711dc23a09ef291f95b7e06c9ba708e35dbe95 SHA-256: 4caa64908b36893b18dca45402ee03d15381c605b6c0f07497f209f73a1c038d

262 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1559.001 Component Object Model

The RTF document contains embedded OLE objects, specifically related to Equation Editor, which strongly indicates exploitation of the CVE-2017-11882 vulnerability. This vulnerability allows for arbitrary code execution when the malicious object is activated. The presence of a large, high-entropy OLE object further supports the payload delivery. No scripts were extracted, and the document body contained only hexadecimal data.

Heuristics 7

Equation Editor OLE1 native payload — CVE-2017-11882 related critical CVE related CVE_2017_11882_RELATED

RTF decodes to an OLE1 Equation.3 embedded object whose native data is large and payload-like, and \objupdate requests automatic activation. This is the delivery shape used by Equation Editor RCE documents such as CVE-2017-11882/CVE-2018-0802, but the malformed MTEF record needed for exact attribution was not recovered.
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.
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 ~3965KB 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
Suspicious extracted artifact info 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.

Extracted artifacts 1

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000000c1.bin` `c86d621f973e2c65c8ffbb7a45b07c8e542926fbce43154cf4a3ede74a464c88`	rtf-objdata-decoded	RTF \objdata at offset 0xC1	1982590 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.99, consistent with packed or encrypted content.

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