Malicious RTF — malware analysis report

Static analysis result for SHA-256 ac574945acc3d8a9…

MALICIOUS

RTF

1.19 MB First seen: 2019-09-30
MD5: ba3249900e8e22c4a7ebde77eadee89e SHA-1: 02246ba17eb9f2edb42b1bae2f030dc1336b765f SHA-256: ac574945acc3d8a9d48cf173a1d52158b9b46d4e70681e6fff1ee31fd2412b61
222 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 ~1139KB 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 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.

Extracted artifacts 7

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000025.bin rtf-objdata-decoded RTF \objdata at offset 0x25 229 bytes
SHA-256: bdf6de0a64b3411ca5229f989a8704bb9f2ac8eac0d3b0c83ab62136585dd012
objdata_01_off0000021e.bin rtf-objdata-decoded RTF \objdata at offset 0x21E 569571 bytes
SHA-256: 5a566ffc9fe73c2018554c974a6855ef4842bbbaa6a4f5cad902e4ffafcb228f
objdata_02_off0011d7c3.bin rtf-objdata-decoded RTF \objdata at offset 0x11D7C3 1123 bytes
SHA-256: 263c6a332f8bed14e4d9417cab11f921ef8d301d5b5d655b5a43179ea58c7434
objdata_03_off0011e0c2.bin rtf-objdata-decoded RTF \objdata at offset 0x11E0C2 32167 bytes
SHA-256: fd4349787a170085f51674defab437a4c62805752f8bda96fe68139f5c2fdc6d
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.60, consistent with packed or encrypted content.
objdata_04_off0012dc48.bin rtf-objdata-decoded RTF \objdata at offset 0x12DC48 404 bytes
SHA-256: 392cac683130eb6402c5b549f0e7d1653f531eebb9a09e8b26c73d30cf6c8b98
objdata_05_off0012dfac.bin rtf-objdata-decoded RTF \objdata at offset 0x12DFAC 937 bytes
SHA-256: e21955e19ee5e9c33caa29d20574aba20d6cc02b855734ac20377ad351eddf3c
objdata_06_off0012e77c.bin rtf-objdata-decoded RTF \objdata at offset 0x12E77C 2633 bytes
SHA-256: ce081fd28fe7177ff803b92dfff0940839fdacbc316318ce15cbf8889540f4f0