RTF malware analysis — malicious · dd3feca5ce42d06d

MALICIOUS

RTF

4.8 KB First seen: 2020-07-02

MD5: 35d4ba1d75cb50f38399352ce84c3cd7 SHA-1: b5bd8020e9477d10fbe9efda44debd64a1416380 SHA-256: dd3feca5ce42d06dce6cec58d86be7aac62f9aba1adfee8227ee2539c806dff9

220 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 related to Equation Editor. High-confidence heuristics indicate the exploitation of CVE-2017-11882, which allows for arbitrary code execution. The presence of shellcode candidate regions further supports this. The file is likely delivered as a spearphishing attachment.

Heuristics 6

Obfuscated Equation Editor ProgID + activation critical CVE related RTF_EQUATION_EDITOR

RTF decodes to an Equation.3 ProgID from top-level \objdata hex after nested RTF junk groups are ignored, and the document also contains \objemb plus \objupdate activation. This is an obfuscated Equation Editor exploit surface associated with CVE-2017-11882 / CVE-2018-0802 families, but no exact malformed MTEF CVE primitive was recovered from this object.
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.
Automatically linked OLE object high RTF_OBJAUTLINK

RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
\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_off00000503.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x503	1784 bytes
SHA-256: `4a76211b07f3b27338ee90e90e85958ae97f37fc350811aec3c69cb334f902db`
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.