RTF malware analysis — malicious · 8057829bd5f8fb2f

MALICIOUS

RTF

650.4 KB Authoring application: Riched20 10.0.17763 First seen: 2020-07-24

MD5: dbb09fd0da004742cac805150dbc01ca SHA-1: b651d655efe5ab72dafec0899eb9088d4183ef61 SHA-256: 8057829bd5f8fb2f40741c2fc32c46ad33ac21d144fef8afdb3ec8b743beb2a8

200 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple indicators of exploitation targeting CVE-2017-11882 via Microsoft Equation Editor. The presence of OLE objects and specific heuristic firings strongly suggest that the file is designed to trigger this vulnerability, leading to arbitrary code execution. No document body text was available for further analysis of user-facing lures.

Heuristics 6

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.
Equation Editor activation — CVE-2017-11882 related high CVE related CVE_2017_11882_ACTIVATION_RELATED

RTF decodes to an Equation.3 ProgID and requests OLE activation with \objemb plus \objupdate. This reaches the legacy Equation Editor attack surface used by CVE-2017-11882/CVE-2018-0802 documents, but the malformed MTEF/native payload needed for stronger attribution was not recovered.
\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 3 \objdata section(s) — embedded OLE objects
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object
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 3

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000000e4.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xE4	331147 bytes
SHA-256: `89159f615e48f9b49406d85616c48123ee61016901a486a0f33601a0963b0abf`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis found candidate code region(s). Indicators: heap spray 0x41 (A) Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off000a1c22.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xA1C22	1710 bytes
SHA-256: `7b9352c9823dc0fdca672b3c841ca510f9d246375cb63526c04fbbb7141b6f0f`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis found candidate code region(s). Indicators: SC_PEB_ACCESS
`objdata_02_off000a1c32.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xA1C32	36 bytes
SHA-256: `8935eb605040753f89379b3f05c2cdaefba833ec64299ed9c258020f4c1217b0`

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