RTF / .DOC malware analysis — malicious · 441ce83f6fb9e054

MALICIOUS

RTF / .DOC

2.14 MB

MD5: 8c9854f8ded9bec2df197290b1e9d877 SHA-1: f112047c810625e8faace372408601d57f61bb2f SHA-256: 441ce83f6fb9e054fc819a7de925bafc22a98995f76d2e985221d2a2589adaa1

262 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1204.002 Malicious File T1059.003 Windows Command Shell T1105 Ingress Tool Transfer

The RTF document contains critical heuristics indicating the exploitation of CVE-2017-11882 through an embedded Equation Editor OLE object. This object decodes to a large, high-entropy binary payload, strongly suggesting it is a second-stage executable. The presence of OLE object data and automatic linking further supports the malicious intent of the document.

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 ~2245KB 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_off000000aa.bin` `c9c5854395967c6e6d433ae8b5ce962119cb963cbe7afec7205ac27bf67c40f4`	rtf-objdata-decoded	RTF \objdata at offset 0xAA	1122944 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.