Malicious RTF — malware analysis report

Static analysis result for SHA-256 88a5bbb95741c125…

MALICIOUS

RTF

408.8 KB First seen: 2019-01-12
MD5: 6f8de20e6b67edefedb8ae8071f24fd4 SHA-1: c62a458aac38920c37ffd481c394a7a940bfef3c SHA-256: 88a5bbb95741c12540ec9ebed53a41e0431933100f114a2e1117b0e30b1dd7e8
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_off0000021a.bin rtf-objdata-decoded RTF \objdata at offset 0x21A 195671 bytes
SHA-256: 3b2f72ab2ae943d66f3050dd8c940cb46e10099d41019770501d40fdf7f2145e
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.86, consistent with packed or encrypted content.
objdata_02_off000635ca.bin rtf-objdata-decoded RTF \objdata at offset 0x635CA 1092 bytes
SHA-256: d4bc1acb790f4d56cd06070639d405330d630c9694d98fa2b3b82c6bf73da07d
objdata_03_off00063e85.bin rtf-objdata-decoded RTF \objdata at offset 0x63E85 636 bytes
SHA-256: beeb549ebc57e264e8e77fa6b4cfd820bf95bef53865f2e41c70d776aef38923
objdata_04_off000643af.bin rtf-objdata-decoded RTF \objdata at offset 0x643AF 393 bytes
SHA-256: cc434f8b829894f9e2d49a62c39440162c7bcebb137b5685ff63adca2384b98a
objdata_05_off000646f5.bin rtf-objdata-decoded RTF \objdata at offset 0x646F5 914 bytes
SHA-256: 27bd5b1e1679863c8cd0257c9eb6b6ee3106b285add9281353de171771ae84d6
objdata_06_off00064e80.bin rtf-objdata-decoded RTF \objdata at offset 0x64E80 2633 bytes
SHA-256: fe11c27d916ab897eb94064e9631d8a29c847a6db39259bef31578da8d19fdf5