RTF malware analysis — malicious · 791b34dba5b49667

MALICIOUS

RTF

488.0 KB First seen: 2021-04-01

MD5: 5c29d4e8c3e0a9d5662b768d2828b78f SHA-1: 50e77de4b07f4ab21e1df77a6c5ccd85c7879d11 SHA-256: 791b34dba5b49667cbc84b91fefcb39cfe2024b10e0dc652e8be738beb599e5a

320 Risk Score

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-0199 / CVE-2017-8759 (OLE2Link auto-activated remote loader) critical CVE related RTF_OLE2LINK_REMOTE_MONIKER_LOADER

RTF embeds an OLE2Link object that is force-activated with \objupdate (no user interaction on open) and fetches a remote second stage — through an INCLUDETEXT/INCLUDEPICTURE field or the OLE object's own moniker. This is the OLE2Link auto-update attack path shared by CVE-2017-0199 (server returns an HTA/scriptlet) and CVE-2017-8759 (server returns a SOAP WSDL the .NET parser compiles). Office processes the fetched response through the same code path; the specific CVE depends on the now-unreachable server content type.
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.
Automatically linked OLE object high RTF_OBJAUTLINK

RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
\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.
Suspicious extracted artifact high 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.
OLE object data medium RTF_OBJDATA

RTF contains 4 \objdata section(s) — embedded OLE objects
Embedded OLE object medium RTF_OBJEMB

RTF contains \objemb — embedded OLE object

Extracted artifacts 4

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off000007f8.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x7F8	141171 bytes
SHA-256: `35fa0d8c48a7763a8bfe4773d044c6e37a76a221ed12da9e4d47d62276973e3d`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): WScript.Shell"")")
`objdata_01_off00004106.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x4106	141145 bytes
SHA-256: `02447b7357150bd6b8723a9d5f07e11d0b42e62c4698cb2c2046e9b625e6b032`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis recovered command string(s): WScript.Shell"")")
`objdata_02_off0004bc75.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x4BC75	2632 bytes
SHA-256: `3cd3b7d42e5855c90d6d11c54ef2670ed8970441480cc23f7d39ef08fa1c935b`
`objdata_03_off0004d218.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x4D218	12297 bytes
SHA-256: `e8d4fe950caed6dcfde26f4b616825bbe11b93458425974b7d075167f675abf7`

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