RTF malware analysis — malicious · 152fde17f279c81b

MALICIOUS

RTF

276.6 KB Created: 2022-06-01 10:55:00 First seen: 2022-06-05

MD5: 58f97b3fe168f08a4d59a8a4a014a09a SHA-1: 4761a14f8a48ba933a8e191d5c3f47ffa89567aa SHA-256: 152fde17f279c81bf2475fb87079fe42226c1ba3a54722fbc43aec5e696362eb

262 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple indicators of exploiting known vulnerabilities, specifically CVE-2017-8570 and CVE-2017-8759, which are known to facilitate the execution of malicious scripts. The presence of OLE object data and composite monikers strongly suggests an attempt to leverage these vulnerabilities for initial execution. The document body, a fake tax invoice, serves as a lure to encourage the user to open the malicious attachment.

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.
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.
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_off0000ae0b.bin` `028fa3dc1c3cf1db2e119424fae15d330700c847e073f097921d60bf1435d1fe`	rtf-objdata-decoded	RTF \objdata at offset 0xAE0B	24324 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off0001744b.bin` `dd004dba58b2c656e3d355d24a17308be9b6544ee8ace220ec7787c93dcaad64`	rtf-objdata-decoded	RTF \objdata at offset 0x1744B	2632 bytes
`objdata_02_off000189ee.bin` `44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037`	rtf-objdata-decoded	RTF \objdata at offset 0x189EE	12297 bytes

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