Malicious RTF — malware analysis report

Static analysis result for SHA-256 ea1889524a7807b5…

MALICIOUS

RTF

468.9 KB First seen: 2019-05-31
MD5: 2c2c43d1d5308e66b97cbfd6f57dc87a SHA-1: b9cba7ffa79850422f9b481c98e2b07aa693941a SHA-256: ea1889524a7807b5bda39c8dab358da0ee683cdffc5791b3a11b998073d9f115
182 Risk Score

Malware Insights

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

The RTF file contains multiple OLE objects and ".objupdate" directives, indicating it is designed to exploit vulnerabilities. Specifically, the "CVE_2017_8570" heuristic firing confirms the use of a Composite Moniker to drop an SCT script, which is a known technique for executing arbitrary code. The embedded OLE object data, particularly at offset 0xB5D2, is the likely source of this exploit.

Heuristics 6

  • 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.
  • 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 204585 bytes
SHA-256: 21c32eb2431fe9521afb92685a737720e63a8cadcebd090f65780fe3b6170a11
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.88, consistent with packed or encrypted content.
objdata_02_off0006d0f1.bin rtf-objdata-decoded RTF \objdata at offset 0x6D0F1 1123 bytes
SHA-256: 263c6a332f8bed14e4d9417cab11f921ef8d301d5b5d655b5a43179ea58c7434
objdata_03_off0006d9f0.bin rtf-objdata-decoded RTF \objdata at offset 0x6D9F0 11441 bytes
SHA-256: 5547c804ed7ffca93c822d20742f1741d3f5ee02b8a53cf7aabd952f5c062696
objdata_04_off0007338a.bin rtf-objdata-decoded RTF \objdata at offset 0x7338A 404 bytes
SHA-256: 392cac683130eb6402c5b549f0e7d1653f531eebb9a09e8b26c73d30cf6c8b98
objdata_05_off000736ee.bin rtf-objdata-decoded RTF \objdata at offset 0x736EE 937 bytes
SHA-256: e21955e19ee5e9c33caa29d20574aba20d6cc02b855734ac20377ad351eddf3c
objdata_06_off00073ebe.bin rtf-objdata-decoded RTF \objdata at offset 0x73EBE 2633 bytes
SHA-256: ce081fd28fe7177ff803b92dfff0940839fdacbc316318ce15cbf8889540f4f0

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