RTF malware analysis — malicious · ff06a30035eba173

MALICIOUS

RTF

21.8 KB First seen: 2020-07-24

MD5: 6b134da318faa11b5dd3df29fff0d87a SHA-1: 8233d57eb9c0569e1dd4c6232167555641e4aae0 SHA-256: ff06a30035eba173931bf5d7a794f2b8202d8106151148bf4b6016a029718384

140 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF document contains an embedded OLE object that leverages a known vulnerability in the Equation Editor component. The heuristic firings indicate that this object is designed to be activated automatically upon opening, leading to the execution of shellcode. This shellcode is likely responsible for downloading and executing a secondary payload, a common technique for initial compromise.

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_off00001dd3.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x1DD3	1689 bytes
SHA-256: `934aa59c67f5ba8c07191ae623b5333e6fee727b905d5f145152e152cd32ab01`
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.