RTF malware analysis — malicious · 21bc34555494cf54

MALICIOUS

RTF

1.30 MB First seen: 2018-11-05

MD5: 09a2d195d39df6231b1b41458fead2ab SHA-1: 312a07a686f540cd24751284cfa6df195c68957d SHA-256: 21bc34555494cf543cff2d9670be494a0821b44b9871c1eb9b94ba19e5091765

240 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution

The RTF file contains multiple indicators of exploitation for CVE-2017-8570, including the presence of Composite Monikers and OLE object data. This vulnerability is known to be used for dropping and executing script files, likely to download and run a second-stage payload. The excessive hex data within OLE objects suggests a hidden payload.

Heuristics 7

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.
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.
Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX

RTF contains ~1157KB of hex-encoded data inside \objdata sections — may hide a payload
OLE object data medium RTF_OBJDATA

RTF contains 7 \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.

Extracted artifacts 7

Files carved from inside the sample during analysis.

Filename	Kind	Source	Size
`objdata_00_off00000025.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x25	229 bytes
SHA-256: `bdf6de0a64b3411ca5229f989a8704bb9f2ac8eac0d3b0c83ab62136585dd012`
`objdata_01_off0000021a.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x21A	578787 bytes
SHA-256: `0eba7ae4ff0a7b30ca787093e6fca693d1156d85e023fa4ae0c174cd54eada7e`
Detection ClamAV: No threats found Obfuscation or payload: likely Static shellcode analysis found candidate code region(s). Indicators: SC_MSF_REVERSE, SC_STR_GETPROCADDRESS, SC_STR_VIRTUALALLOC Static shellcode analysis recovered API/import strings: LoadLibraryA, GetProcAddress, VirtualAlloc, CreateFileW, advapi32.dll, shell32.dll
`objdata_02_off00145392.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x145392	1116 bytes
SHA-256: `93ac402ce898ee6f1b9e776ff4289854d3037d6d65706352bd0b71bc418a2ddd`
`objdata_03_off00145c7d.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x145C7D	10440 bytes
SHA-256: `91579808fb353f7087ab5da760b34911e49538e8c60b80ff072ec246b59015da`
`objdata_04_off0014ae3f.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x14AE3F	399 bytes
SHA-256: `dc3da5e38801b5fa23cf99248f674a9b06d9120c119f995001155e4bc263978f`
`objdata_05_off0014b191.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x14B191	937 bytes
SHA-256: `e21955e19ee5e9c33caa29d20574aba20d6cc02b855734ac20377ad351eddf3c`
`objdata_06_off0014b94a.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x14B94A	2633 bytes
SHA-256: `27c6d10cfe7974ebf40c1200cc005f9878cc37b7d49ece9cbc396d700c38918a`

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