Malicious RTF — malware analysis report

Static analysis result for SHA-256 392cbe896ab676dd…

MALICIOUS

RTF

1.40 MB First seen: 2019-04-17
MD5: 018f7554cf2f36687cb2ba6800d60c39 SHA-1: 62a61f4b05192714fbca808589f093eadad3ba3c SHA-256: 392cbe896ab676ddaf08cdcddc96b2e0a3150ce00e8119ba052daf677246f4a9
242 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains multiple indicators of malicious activity, including the presence of OLE objects and a Composite Moniker, strongly suggesting exploitation of CVE-2017-8570. This vulnerability is known to drop and execute SCT scripts. The heuristic 'CVE_2017_8570' specifically points to this exploit, which facilitates client execution by dropping a script. The presence of a large, hex-encoded OLE object further supports the likelihood of a hidden payload.

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.
  • 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 ~1377KB 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.
  • 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.openxmlformats.org/drawingml/2006/main In RTF body

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 688867 bytes
SHA-256: c45118c0b0b9e451b139634a417677700cb17bfcf003a9c022817b2de84e2662
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis found candidate code region(s). Indicators: SC_MSF_REVERSE, SC_STR_VIRTUALALLOC, SC_STR_LOADLIBRARY Static shellcode analysis recovered API/import strings: LoadLibraryExA, VirtualAlloc, GetProcAddress, ExitProcess, kernel32.dll, KERNEL32.DLL
objdata_02_off00155ad9.bin rtf-objdata-decoded RTF \objdata at offset 0x155AD9 1123 bytes
SHA-256: 263c6a332f8bed14e4d9417cab11f921ef8d301d5b5d655b5a43179ea58c7434
objdata_03_off001563d8.bin rtf-objdata-decoded RTF \objdata at offset 0x1563D8 31460 bytes
SHA-256: b30fc706e3044d6a9a2cfc9db1bd0f3e8acaf676ffd7c63484f5e67381ce83b4
objdata_04_off001659d8.bin rtf-objdata-decoded RTF \objdata at offset 0x1659D8 404 bytes
SHA-256: 392cac683130eb6402c5b549f0e7d1653f531eebb9a09e8b26c73d30cf6c8b98
objdata_05_off00165d3c.bin rtf-objdata-decoded RTF \objdata at offset 0x165D3C 937 bytes
SHA-256: e21955e19ee5e9c33caa29d20574aba20d6cc02b855734ac20377ad351eddf3c
objdata_06_off0016650c.bin rtf-objdata-decoded RTF \objdata at offset 0x16650C 2633 bytes
SHA-256: ce081fd28fe7177ff803b92dfff0940839fdacbc316318ce15cbf8889540f4f0