Malicious RTF — malware analysis report

Static analysis result for SHA-256 23a35215faceea0e…

MALICIOUS

RTF

413.4 KB First seen: 2019-05-16
MD5: c3949402d9ff4edda5e79f53509eec50 SHA-1: efd8461e98823edb8af7df54ac9d912749d2568f SHA-256: 23a35215faceea0ee9b9ae183e5cdfbc3eaf551677bdda517d23ef2e6d091a30
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 9 \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 8

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000025.bin rtf-objdata-decoded RTF \objdata at offset 0x25 205 bytes
SHA-256: 980870ba17beb12f03c3941a0cfa655d820816cec9104090156a6ea6ece5ce8a
objdata_01_off000001ee.bin rtf-objdata-decoded RTF \objdata at offset 0x1EE 195527 bytes
SHA-256: 079d0477bd678f350b82e0c95dc822198055d30a46278a62d3efbb27ea4f3f4e
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.87, consistent with packed or encrypted content.
objdata_02_off00063485.bin rtf-objdata-decoded RTF \objdata at offset 0x63485 990 bytes
SHA-256: 819742f5c84cbe7b646f281a2d66b550ab90b6860c2f5bde5cdca478f30b59a9
objdata_03_off00063c7a.bin rtf-objdata-decoded RTF \objdata at offset 0x63C7A 612 bytes
SHA-256: c62851521e10316dfd43f2b6ee67cc27e2a24456bb346c8fa9dc4a6d6e21d526
objdata_04_off0006417a.bin rtf-objdata-decoded RTF \objdata at offset 0x6417A 380 bytes
SHA-256: 17e63036be0dbac77e35be89dbbfbf4e8c5055136fd574d2fd6018a721b22af7
objdata_05_off000644ae.bin rtf-objdata-decoded RTF \objdata at offset 0x644AE 882 bytes
SHA-256: e0dd860bb62dee2108b913a024deb7f63abfad8765c6af0041159382d16d8717
objdata_06_off00064c10.bin rtf-objdata-decoded RTF \objdata at offset 0x64C10 2633 bytes
SHA-256: fe11c27d916ab897eb94064e9631d8a29c847a6db39259bef31578da8d19fdf5
objdata_07_off00066128.bin rtf-objdata-decoded RTF \objdata at offset 0x66128 2601 bytes
SHA-256: 67ff079a9b0f053ca2843811d9da7a8fdedc7d9d377ef39d09dde148b9657c7f