RTF / .DOC malware analysis — malicious · 802c56b6f190b1e7

MALICIOUS

RTF / .DOC

1.57 MB

MD5: 70835af508eabf02ab3e551d360651d1 SHA-1: 35a9bafb02a4ae22df4fd76d4da2ae8d6e3868d1 SHA-256: 802c56b6f190b1e7bb65ab1b6c82cfaa62724fe1cb4fa0c0c4acd1061064f952

262 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains an embedded OLE object that leverages the Equation Editor vulnerability (CVE-2017-11882). This vulnerability is known to be used for executing arbitrary code. The presence of a high-entropy PE artifact within the decoded OLE object strongly suggests that a malicious payload is being delivered and executed.

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.
Decoded Equation Editor payload + PE critical RTF_EQUATION_EDITOR

RTF decodes to an Equation Editor ProgID adjacent to OLE activation and the same decoded object stream contains embedded PE bytes. This matches the Equation Editor exploit surface used by CVE-2017-11882 / CVE-2018-0802 documents, while requiring payload evidence to avoid flagging benign Equation references.
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 ~1648KB of hex-encoded data inside \objdata sections — may hide a payload
OLE object data medium RTF_OBJDATA

RTF contains 1 \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_off0000006a.bin` `4dad39294b8a6c59f74cc454bee93a6b0d30386dec4dfc52444747546f60e948`	rtf-objdata-decoded	RTF \objdata at offset 0x6A	824127 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.