RTF malware analysis — malicious · 8e0309f78d509b5a

MALICIOUS

RTF

35.5 KB First seen: 2019-01-12

MD5: 4529ec3836b4b712daa0d8839a6dcdea SHA-1: 12f7fa73930f30f7b82c7d1d47653f688c2b795c SHA-256: 8e0309f78d509b5a3c3d337567b72ca6b7b6d675d94d6bdadb0983fd504b82a9

140 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains embedded OLE object data and specifically triggers heuristics for a split hex Equation Editor ProgID and ".objupdate" forcing OLE activation. This indicates exploitation of a known vulnerability in the Equation Editor component, commonly used to achieve arbitrary code execution. The extracted artifact "objdata_00_off00007e07.bin" is likely shellcode or a payload dropper.

Heuristics 4

Split hex Equation Editor ProgID + OLE object critical CVE likely 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.
OLE object data medium RTF_OBJDATA

RTF contains 1 \objdata section(s) — embedded OLE objects
Suspicious extracted artifact medium 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_off00007e07.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x7E07	2020 bytes
SHA-256: `296ee0c41656cd750e8094b0591f7c5245f46dc9ed1a11ef77a9543f2966c99e`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis found candidate code region(s). Indicators: SC_GETPC_CALL

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