RTF / .DOC malware analysis — malicious · f59334e00c6d110e

MALICIOUS

RTF / .DOC

6.48 MB

MD5: 9c3f6880aded8d9c315adf9d7d8eb71f SHA-1: 1a1e118d78e384ee6e670ccf668616c50084b2c9 SHA-256: f59334e00c6d110e48fbd558c30c0c0d412f64eb0da1493236c9464b442d713b

222 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Phishing: Spearphishing Attachment

The RTF document contains an embedded OLE object that leverages the Equation Editor vulnerability (CVE-2017-11882). This exploit is designed to execute a secondary payload, likely a downloader or dropper, which is hidden within the large, high-entropy OLE object data. The presence of multiple critical heuristics related to Equation Editor and OLE object manipulation strongly indicates this attack vector.

Heuristics 6

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.
\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 ~6789KB 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_off000000ca.bin` `4b3bc1c31432bd99200de177a8a29a8712df1a8422d66dc77de04d2b2166912f`	rtf-objdata-decoded	RTF \objdata at offset 0xCA	3394885 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 8.00, consistent with packed or encrypted content.

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