Malicious RTF — malware analysis report

Static analysis result for SHA-256 7e21ef92d1f7c992…

MALICIOUS

RTF

1.42 MB First seen: 2019-11-20
MD5: a494766d81aad49676540ef02b4e5154 SHA-1: 79a543fb751b70ee9a6c11443ca3a995068dcbcf SHA-256: 7e21ef92d1f7c992856ed45284f7c82497341b4490fe723f50f16ea27b06323b
240 Risk Score

Malware Insights

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

The RTF file contains multiple OLE objects with excessive hex data, indicative of a hidden payload. Specifically, the presence of a composite moniker and the CVE-2017-8570 heuristic strongly suggest the file is designed to drop and execute a script, likely a second-stage payload. The embedded artifacts, particularly objdata_00_off0001baee.bin and objdata_02_off00168830.bin, are suspicious and likely contain malicious code.

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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~1475KB of hex-encoded data inside \objdata sections — may hide a payload
  • Suspicious extracted artifact high 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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 5 \objdata section(s) — embedded OLE objects

Extracted artifacts 5

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0001baee.bin rtf-objdata-decoded RTF \objdata at offset 0x1BAEE 681129 bytes
SHA-256: 921b43e59fd8a867a2ce2afefe5533d7c3e5132d88b96010a0a6d5313e709ee6
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.
objdata_01_off00168481.bin rtf-objdata-decoded RTF \objdata at offset 0x168481 444 bytes
SHA-256: 9a92e9b52588416922da9ff504d0e13de10f7c9209a209170102cf83da970296
objdata_02_off00168830.bin rtf-objdata-decoded RTF \objdata at offset 0x168830 1245 bytes
SHA-256: 2703dc2ca3c0d9e8edd5a157bc15cef46ae50607824244b9311f26196efc1de5
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): cscript //nologo %vbs%
objdata_03_off00169220.bin rtf-objdata-decoded RTF \objdata at offset 0x169220 1178 bytes
SHA-256: 421d42edb91323a580f04b37e14277df2c3453a620830f900d07f86ca61f65f2
objdata_04_off00169bc3.bin rtf-objdata-decoded RTF \objdata at offset 0x169BC3 2633 bytes
SHA-256: c652d237d34511cfc2908b6727831912f33e6dd1c0a558d188cd3c8467dd6026