RTF / .DOC malware analysis — malicious · b31c40e0a0b0d0eb

MALICIOUS

RTF / .DOC

1.03 MB

MD5: 7bef5fb567fce9e0b5f26a927bfecfb5 SHA-1: ff8790f274ec842cd7eaa8a760b44fe89a9aab2c SHA-256: b31c40e0a0b0d0ebc611207ff6b3310317abd0da06869fd3b437015130b640fe

222 Risk Score

Malware Insights

MITRE ATT&CK

T1204 Malicious Link T1059 Command and Scripting Interpreter T1566 Phishing

The sample is an RTF document containing an embedded OLE object that exploits the Equation Editor vulnerability (CVE-2017-11882). The presence of `RTF_EQUATION_EDITOR` and `CVE_2017_11882_RELATED` heuristics strongly indicates this exploit. The `SC_STR_MSHTA` heuristic suggests that mshta.exe may be used to execute the payload, likely downloaded or staged by the embedded object. No document body or scripts were extracted, but the exploit itself is sufficient to classify the attack pattern.

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.
Reference to mshta.exe high SC_STR_MSHTA

Reference to mshta.exe
\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.
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_off0000008e.bin` `053fe4720a72c4e17c14cee9c70c31c0727b19d54eac088b6e52d90b9bb155a2`	rtf-objdata-decoded	RTF \objdata at offset 0x8E	500504 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.98, consistent with packed or encrypted content.

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