RTF / .DOC malware analysis — malicious · 15635f4f8ddb6bc7

MALICIOUS

RTF / .DOC

1.08 MB Created: 2023-01-23 21:13:00 First seen: 2023-01-24

MD5: 4cffd63038352505d973a5a937b6139d SHA-1: 995e4a6b9b2bce67294057b8818259df71644f94 SHA-256: 15635f4f8ddb6bc79a78b0cbec03da9548054d207d1fe094eb390e9ae2052422

302 Risk Score

Malware Insights

MITRE ATT&CK

T1204 Malicious Link T1204.002 Malicious Link: Malicious File T1059 Command and Scripting Interpreter T1566 Phishing T1566.001 Phishing: Spearphishing Attachment

The file is an RTF document that contains embedded OLE objects, triggering heuristics related to CVE-2017-8570 and CVE-2017-8759. These vulnerabilities are known to be exploited for dropping and executing scripts. The document body, formatted as a budget or invoice, serves as a lure to trick the user into opening the malicious content. The presence of multiple OLE object-related heuristics and specific CVE firings strongly indicates an exploit attempt.

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.
\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 ~1023KB of hex-encoded data inside \objdata sections — may hide a payload
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.
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/word/2003/wordml

Extracted artifacts 3

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000d5dd1.bin` `caa878f61f59f4b49f1b78d4004a065cc702ea78b92a5119a10b42f5024d4b7e`	rtf-objdata-decoded	RTF \objdata at offset 0xD5DD1	34291 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off000e750b.bin` `24fedef2d4fe5e3d6666fae2543850c54134511ad6be8583d5aa0438ef699c5d`	rtf-objdata-decoded	RTF \objdata at offset 0xE750B	2632 bytes
`objdata_02_off000e8aae.bin` `142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78`	rtf-objdata-decoded	RTF \objdata at offset 0xE8AAE	12297 bytes

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