RTF malware analysis — malicious · b5aba8f35aff24b2

MALICIOUS

RTF

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

MD5: a43365525d2d7261c3bd3ca9a40c7669 SHA-1: 0c1e1ff0b0c97d46ba097125e444e8d2939ed5bc SHA-256: b5aba8f35aff24b29b9a6b01de654b848d29406c63294b94a7d412feb0544063

322 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple high and critical heuristic firings indicating the exploitation of CVE-2017-8570 and CVE-2017-8759. These vulnerabilities are known to be used for dropping and executing scripts, such as SCT files, via OLE object manipulation. The presence of OLE objects and automatic update flags strongly suggests an attempt to execute a secondary payload.

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: `0248543bbc1eeea2c5f24041d3c88c594de33f97589efd3e370aa6750c93808a`
`objdata_01_off00019a70.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x19A70	59568 bytes
SHA-256: `6e087861e2dbb44b5fc22f97d027b70fce5c6ae827d87aaf4cbfb21496633358`
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.