RTF / .DOC malware analysis — malicious · 3a73399f45a1ea64

MALICIOUS

RTF / .DOC

381.8 KB Created: 2022-09-12 First seen: 2022-09-20

MD5: 6fe8ae16a74f5d8cf870edbb77d8dda5 SHA-1: 6c9c6bc6482889733e0ba06f80a322e1c3f0857f SHA-256: 3a73399f45a1ea64fc8825a8766c7b2b913ecbf226519912786418697f83bbce

262 Risk Score

Malware Insights

MITRE ATT&CK

T1204 Malicious Link T1059 Command and Scripting Interpreter T1566 Phishing

The file is an RTF document that leverages multiple critical vulnerabilities (CVE-2017-8570 and CVE-2017-8759) related to OLE object activation and composite monikers. These vulnerabilities are known to facilitate the execution of arbitrary code, typically to download and run a secondary malicious payload. The document body discusses subsidy systems, a common lure for phishing or social engineering attacks.

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_off0000bf1f.bin` `0953a3f36fd187c22171cbf1e2721130acef35f180be136996a4bebe914677cb`	rtf-objdata-decoded	RTF \objdata at offset 0xBF1F	74037 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off00031949.bin` `43dc420203828d24ec36adf809a9ada54bc1f182c6dd7bd39e852b7059bf1a1d`	rtf-objdata-decoded	RTF \objdata at offset 0x31949	2632 bytes
`objdata_02_off00032eec.bin` `142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78`	rtf-objdata-decoded	RTF \objdata at offset 0x32EEC	12297 bytes

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