RTF malware analysis — malicious · 8f2fa0b2ae14a325

MALICIOUS

RTF

19.9 KB First seen: 2020-09-07

MD5: 682aed86c575f8637d11b0c01bc06cb4 SHA-1: 6131ff5f6644a2a3c24dca040fd027e011b32c9f SHA-256: 8f2fa0b2ae14a325f866335bb72a9ece7c49ed2a003b5298f1eafaa8714953eb

140 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains an embedded OLE object with a split Equation Editor ProgID, indicating exploitation of a known vulnerability (CVE-2017-11882). The \objupdate directive forces OLE activation, and a shellcode candidate region was identified within the extracted objdata. This strongly suggests the file is designed to execute arbitrary code, likely for downloading and running a further stage.

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_off00001228.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x1228	1837 bytes
SHA-256: `d73c9dfc4aaf17a18abf38cb55292082bf9fc36099c145fb4ff0618f28a5de8c`
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.