Malicious RTF — malware analysis report

Static analysis result for SHA-256 5dc1511c523b9f44…

MALICIOUS

RTF

477.3 KB First seen: 2023-02-06
MD5: c4d46abe171ce13b33ac78deb2ffa795 SHA-1: a58bb2cf552a08c3603e42ab5d245359f5ab2dfd SHA-256: 5dc1511c523b9f44580ede70726f3d2acb439de04feeb5bddd1b037005dc5d50
200 Risk Score

Malware Insights

MITRE ATT&CK
T1204 Malicious File Execution T1059 Command and Scripting Interpreter T1059.003 Windows Command Shell

The RTF file contains OLE object data and triggers ".objupdate" which are indicative of exploitation. Specifically, the "CVE_2017_8570" heuristic firing points to the use of a Composite Moniker to drop an SCT script, a known technique for executing malicious code. The embedded document body appears to be a fake invoice, suggesting a social engineering lure to trick users into opening the malicious RTF file.

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 3 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object
  • Suspicious extracted artifact medium 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 3

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000378b4.bin
4dcc25acc13956d519deebccf70676fb95d28df1813720363cb16996977cea9b
rtf-objdata-decoded RTF \objdata at offset 0x378B4 35148 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 shell/COM execution token(s).
objdata_01_off000496e6.bin
24fedef2d4fe5e3d6666fae2543850c54134511ad6be8583d5aa0438ef699c5d
rtf-objdata-decoded RTF \objdata at offset 0x496E6 2632 bytes
objdata_02_off0004ac89.bin
142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78
rtf-objdata-decoded RTF \objdata at offset 0x4AC89 12297 bytes