RTF malware analysis — malicious · 1024c07c34beee19

MALICIOUS

RTF

408.6 KB Created: 2020-06-09 12:34:00 First seen: 2021-07-07

MD5: a841a73e09e73e8bc6c8ee5270c1a434 SHA-1: bb57fae09a0bf544ac33df6dfc3cc50d9ea8ffb7 SHA-256: 1024c07c34beee1911abb9179f96989859fe7ecb9601a8d27c28add7fdbb8d73

322 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple indicators of exploitation, specifically referencing CVE-2017-8570 and CVE-2017-8759, which are known to facilitate arbitrary code execution. The presence of OLE objects and composite monikers strongly suggests an attempt to leverage these vulnerabilities to drop and execute a script or payload. The document body content appears to be garbled or malformed, providing no clear lure, but the technical indicators point towards a malicious exploit.

Heuristics 9

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.
CVE-2017-8759 — MSXML SAX OLE activation critical CVE likely CVE_2017_8759

RTF contains a hex-encoded OLE1 object for Msxml2.SAXXMLReader.6.0 followed by an embedded OLE compound document, and the document requests OLE activation. This matches the RTF staging shape used for CVE-2017-8759 SOAP/WSDL parser code injection.
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.
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.
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 4 \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://schemas.microsoft.com/office/w In RTF body

Extracted artifacts 4

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000132c1.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x132C1	59595 bytes
SHA-256: `774bb4416a2562cba43bb6db7a74f9cf83b0c84cd6b58bd352c1ef6fe9182774`
`objdata_01_off00019a70.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x19A70	59568 bytes
SHA-256: `0630fb66d1151e7c532d1c5a192e0e671ece12cc1d7adacd9c859d8c53a0dd09`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): WScript.Shell"")")
`objdata_02_off00037f0f.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x37F0F	2632 bytes
SHA-256: `a8e170497da15decc11753d202c99c86f7a7ffd2d52481e6b9c79a5403675379`
`objdata_03_off000394b2.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x394B2	12297 bytes
SHA-256: `e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7`

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