RTF malware analysis — malicious · cc7a20ddeab4a36f

MALICIOUS

RTF

4.5 KB First seen: 2019-02-10

MD5: ba9d0949766bd4095101fda80425b100 SHA-1: 5689a8be0de50ef96f9d52f2473414691c65fc65 SHA-256: cc7a20ddeab4a36f474041e17575594bee0ec2893498df1b136a9e9a2ea732ed

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, specifically identified as a vulnerable Equation Editor object. The ".objupdate" directive forces the activation of this object, which is known to exploit a client execution vulnerability. This likely leads to the download and execution of a secondary payload, as indicated by the 'Shellcode candidate region' heuristic.

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_off0000003c.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x3C	2297 bytes
SHA-256: `75e0f18ad8e9b5eb7ad76079a955053ec6cd853136f1ed66221d59286c4eff8b`
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.