RTF / .DOC malware analysis — malicious · 14ef41226f7b85fe

MALICIOUS

RTF / .DOC

1.05 MB First seen: 2023-05-29

MD5: aa39d097f6a70f0de3014026c22a4b9f SHA-1: 5b6943d9fc76f937220fa16bf883f8108b1e6836 SHA-256: 14ef41226f7b85fefd60d3fe5762108540aa0daea19d5b6d4a55764270cc6e0d

262 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains an OLE object that exploits the Equation Editor vulnerability (CVE-2017-11882). This vulnerability allows for the execution of arbitrary code, and the heuristics indicate a PE file was decoded from the object data. The presence of ".bin" in the extracted artifact name suggests a potential secondary payload.

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 ~1105KB 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_off00000093.bin` `e9741f74611a9f2c468da805d7a1e0b8478052d7ff44c21d58e46104adb81117`	rtf-objdata-decoded	RTF \objdata at offset 0x93	552762 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.