RTF malware analysis — malicious · 2b2a256e06236b38

MALICIOUS

RTF

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

MD5: 368ae8a3896c3d792acb19e55550b188 SHA-1: acd2a3dcdfe7087653a7ea955bd1c1fe9fddfd73 SHA-256: 2b2a256e06236b381a512a12f399ac24c8e58957060034d1f74691c0454b4607

202 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF document contains multiple OLE objects, with specific heuristics indicating the use of \objupdate and Composite Monikers. Critically, the CVE-2017-8759 heuristic fires, confirming exploitation of a known vulnerability in MSXML SAX for OLE activation. The document body is a lure for a fake tax invoice, suggesting a social engineering pretext for the malicious payload delivery. No scripts were extracted, but the OLE object activation is sufficient to indicate a payload execution attempt.

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` `4c342d1b940e335143525f7b7c98e3dce95f63022c78edd41f95b663237cb584`	rtf-objdata-decoded	RTF \objdata at offset 0xAE0B	24308 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact contains 1 shell/COM execution token(s).
`objdata_01_off00017429.bin` `dd004dba58b2c656e3d355d24a17308be9b6544ee8ace220ec7787c93dcaad64`	rtf-objdata-decoded	RTF \objdata at offset 0x17429	2632 bytes
`objdata_02_off000189cc.bin` `44deae4627fee3c44f54d5bd10477ec2e17f4c08135f08e2417832e36d10d037`	rtf-objdata-decoded	RTF \objdata at offset 0x189CC	12297 bytes

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