RTF malware analysis — malicious · f2779c63373e33fd

MALICIOUS

RTF

416.4 KB Created: 2022-01-18 01:21:00 First seen: 2022-10-22

MD5: 5c882934fb0b14fff46300e607201944 SHA-1: dd4464e773fcc3f39b16007fc03874b55e6f31ca SHA-256: f2779c63373e33fdbd001f336df36b01b0360cd6787c1cd29a6524cc7bcf1ffb

224 Risk Score

Malware Insights

MITRE ATT&CK

T1204 Malicious Link T1204.001 Malicious Link: Malicious Link T1559 Component Object Model Hijacking T1559.001 Component Object Model Hijacking: Component Object Model Hijacking

The RTF file contains multiple OLE objects and utilizes \objupdate to force OLE activation. Crucially, it fires the CVE-2017-8759 heuristic, indicating exploitation of MSXML SAX OLE activation. This suggests the file is designed to leverage this vulnerability to execute malicious code or load further stages.

Heuristics 8

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.
Ole10Native stream in RTF OLE object high CVE related RTF_OLE10NATIVE_STREAM

RTF contains an embedded OLE object with an Ole10Native stream. This is a strong payload-container signal and is related to Word/OLE exploit delivery, but it is not specific enough on its own to assign a CVE.
Heap-spray pattern detected high SC_HEAP_SPRAY

Repeated 0x41 (A) bytes found
\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 info 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_off000078ad.bin` `814a03da447c315cbc7e7a339fc46e199d23e98c6d92338c2694f18a0b8864e0`	rtf-objdata-decoded	RTF \objdata at offset 0x78AD	187432 bytes
Detection ClamAV: No threats found Obfuscation or payload: likely Carved artifact entropy is 7.98, consistent with packed or encrypted content.
`objdata_01_off000635f4.bin` `873dcfc92c85580fd96689a2951cf454a14d06501e2a3f73d429956129562343`	rtf-objdata-decoded	RTF \objdata at offset 0x635F4	8896 bytes
`objdata_02_off0006360e.bin` `5af2d0d4f8b1d492a6e14673f7a073da0d016e6f6e14547a2bd976f581c2b6e2`	rtf-objdata-decoded	RTF \objdata at offset 0x6360E	8892 bytes

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