Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 39e6d2cfe42c41a7…

MALICIOUS

RTF / .DOC

257.0 KB First seen: 2023-01-30
MD5: fddce2b3c97faecb1feb8fea47edf53e SHA-1: c5fdcd9c686970724faee24edab87663a16e92eb SHA-256: 39e6d2cfe42c41a7d571ed30431236b6383b064e1ff0b72757457e9cc4ae46c1
200 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File Execution: Malicious File T1566.001 Phishing: Spearphishing Attachment

The RTF file contains OLE object data and triggers ".objupdate" which are indicative of exploitation. Specifically, the "CVE_2017_8570" heuristic firing confirms the use of a composite moniker to drop an SCT script. This script is likely intended to download and execute a second-stage payload, making this a downloader or initial access mechanism.

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_off000007d4.bin
2aa264605f5902ee17a30514bf31c470f1e7e38eed4597a2d918cd3c440f2a75
rtf-objdata-decoded RTF \objdata at offset 0x7D4 35098 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 shell/COM execution token(s).
objdata_01_off0001259e.bin
24fedef2d4fe5e3d6666fae2543850c54134511ad6be8583d5aa0438ef699c5d
rtf-objdata-decoded RTF \objdata at offset 0x1259E 2632 bytes
objdata_02_off00013b41.bin
142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78
rtf-objdata-decoded RTF \objdata at offset 0x13B41 12297 bytes