RTF / .DOC malware analysis — malicious · fbc12470553e748b

MALICIOUS

RTF / .DOC

2.82 MB

MD5: 5a0c6dd1f7bbc5272f2ced270e2d4d8a SHA-1: 9f553e08793745277db8a0d3aa82a63b7526a28b SHA-256: fbc12470553e748b10dd0e1a15c6e28a1e777b626757349e46031f7e0608b8e6

262 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1027 Obfuscated Files or Information

The RTF document contains embedded OLE object data, specifically triggering critical heuristics for CVE-2017-11882 related to the Equation Editor. This indicates the file is designed to exploit this vulnerability to execute a payload. The large amount of hex-encoded data within the OLE object further suggests it is used to hide the malicious 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.
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 ~2918KB 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_off000000b4.bin` `a8bd4fee5bc212b295c3f3efe85b31b95af5008ea1e4d810f98627c348ac2b63`	rtf-objdata-decoded	RTF \objdata at offset 0xB4	1464258 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.