RTF malware analysis — malicious · 522eb4b0179fcc99

MALICIOUS

RTF

2.08 MB First seen: 2019-12-09

MD5: 369a2dc3da6ba652a7c30f61abea43cc SHA-1: cb2e8396875fa14b6246e401a10c79d3e6dc8908 SHA-256: 522eb4b0179fcc99d8a1a48095751fa3ae05c78ed021133d8ad7436ba562678a

262 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution

The sample is an RTF file that leverages a Composite Moniker to exploit CVE-2017-8570. This vulnerability allows the RTF document to drop an embedded OLE object, which in this case is identified as a suspicious executable file. The embedded URL suggests the downloaded payload is named 'drive.exe'. The exploitation of a known vulnerability for client execution is the primary attack vector.

Heuristics 8

Composite Moniker — CVE-2017-8570 (drops SCT script) critical CVE related CVE_2017_8570

RTF \objdata decodes to OLE data containing the Composite Moniker — CVE-2017-8570 (drops SCT script) CLSID — the vulnerable control/moniker is embedded directly in the document's object stream, the delivery shape of this exploit. RTF objects auto-render when Word opens the file.
Composite Moniker in RTF OLE object high CVE related RTF_COMPOSITE_MONIKER_RELATED

RTF contains Composite Moniker CLSID in OLE object context, but no nearby scriptlet/SCT payload was confirmed. Treat as related moniker attack-surface evidence rather than proof of CVE-2017-8570 exploitation.
\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.
Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX

RTF contains ~1079KB of hex-encoded data inside \objdata sections — may hide a payload
Suspicious extracted artifact high 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.
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
Embedded URL info EMBEDDED_URL

One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.

URL http://188.209.52.180/drive.exe In RTF body

Extracted artifacts 3

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00004fc6.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x4FC6	4691 bytes
SHA-256: `6a2038c1bdbad9f5f6e8c35d8b964460ff392ee1ec2c566117eb8b7f530184b6`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): WScript.Shell") 'owcmwdkom ev feefp vpvfeoo fveio fvefe ofe btwoe woeifjoweij weiowehif wghy
`objdata_01_off0010c948.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x10C948	977 bytes
SHA-256: `3973ac75095c94c9ecd9f138a4740d01e3efa5eeb0eb0be7385592db2de8d47c`
`objdata_02_off0010d0f7.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x10D0F7	3621 bytes
SHA-256: `0745a1c17cf9be2e09e8a3c99743313a0ece40871cd2ec57f5f8c593eace973c`

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