Malicious RTF — malware analysis report

Static analysis result for SHA-256 ae99234f0ecfba47…

MALICIOUS

RTF

926.0 KB First seen: 2019-05-10
MD5: fbb5e0cf91d05e022e7f178c07d53ccf SHA-1: 4c2574260a4f54852bfb175c6516d2be23545c85 SHA-256: ae99234f0ecfba47bbd49e095578a417b503414597a32b72fbe918546a1b9a87
200 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 OLE object data and composite moniker structures. Specifically, the CVE-2017-8570 heuristic firing indicates the file is designed to drop a script, likely for execution. This points to an exploitation attempt for client execution, often delivered via spearphishing attachments.

Heuristics 5

  • 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.
  • 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_off00018659.bin rtf-objdata-decoded RTF \objdata at offset 0x18659 461 bytes
SHA-256: 206de2c9cd9db0d53e41bfcdc530ad5e19e7c3176125a5695cb462e4b91897b1
objdata_01_off00018a23.bin rtf-objdata-decoded RTF \objdata at offset 0x18A23 1461 bytes
SHA-256: 8df7f9c2123e9d6f06a64f7d213e3d1b3d14d9d76df3272b5826a9f0d534c937
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Static shellcode analysis recovered command string(s): cscript //nologo %vbs%
objdata_02_off000195bb.bin rtf-objdata-decoded RTF \objdata at offset 0x195BB 1260 bytes
SHA-256: 5e60dfd240a20741904a8370aa4d813777d27d73f2509aafae0d3abf0987dd37
objdata_03_off00019fbd.bin rtf-objdata-decoded RTF \objdata at offset 0x19FBD 2633 bytes
SHA-256: c652d237d34511cfc2908b6727831912f33e6dd1c0a558d188cd3c8467dd6026
objdata_04_off0001b488.bin rtf-objdata-decoded RTF \objdata at offset 0x1B488 418225 bytes
SHA-256: e6de46be82550f15933f5eb6ca942faa64d292322b647989531b0dd4d8a2ca02
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.