RTF / .DOC malware analysis — malicious · a10b62cee82e9ef6

MALICIOUS

RTF / .DOC

276.4 KB Created: 2022-06-01 10:55:00 First seen: 2022-06-08

MD5: 883415b5c38501b0a86c1f1644d9de6b SHA-1: 457108e7e8f74f8028293791d9d38df95fc9686a SHA-256: a10b62cee82e9ef618dc5b4f1d391fea31b92d472ae43f20b0c52964df103ced

202 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains embedded OLE objects, with specific heuristics indicating the use of \objupdate to force OLE activation. This strongly suggests exploitation of CVE-2017-8759, a known vulnerability in MSXML that allows for remote code execution when a malicious OLE object is activated. The document body, a fake invoice, serves as a lure to encourage user interaction and trigger the exploit.

Heuristics 7

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}}\paperw12240\paperh15840\margl1440\margr1440\margt1440\margb1440\gutter0\ltrsect

Extracted artifacts 3

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off0000ae0b.bin` `41e6164b2e02cf5ff8800c78e64219342a6bfb2a02e17672419fd80ad0b70f62`	rtf-objdata-decoded	RTF \objdata at offset 0xAE0B	24255 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off000173bb.bin` `dd004dba58b2c656e3d355d24a17308be9b6544ee8ace220ec7787c93dcaad64`	rtf-objdata-decoded	RTF \objdata at offset 0x173BB	2632 bytes
`objdata_02_off0001895e.bin` `44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037`	rtf-objdata-decoded	RTF \objdata at offset 0x1895E	12297 bytes

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