Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 5a5520eb74cab558…

MALICIOUS

RTF / .DOC

229.8 KB First seen: 2022-07-14
MD5: 2d5a176ad442957af8748a6d5f62f1a7 SHA-1: d7001b289c3d283502285b344c524ab5444901b1 SHA-256: 5a5520eb74cab558e515a0693a6d10fcf244224ed9368225633c4a6d288ad2c2
220 Risk Score

Malware Insights

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

The RTF document contains OLE object data and triggers heuristics related to CVE-2017-8570, which is known to drop SCT scripts. The document body explicitly instructs the user to 'click Enable Editing when opening', indicating a social engineering lure to bypass security measures. The embedded artifact objdata_00_off0000095c.bin is likely the dropped script, which would then execute the exploit.

Heuristics 7

  • 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
  • Macro/content-enable lure medium SE_ENABLE_LURE
    Document instructs the user to enable macros or editing — a common technique used by malware droppers to bypass Office macro security settings
  • 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_off0000095c.bin
ef64edb57026eb901f1409f3af55a4b89bbe454711543ae091888278b0e9926b
rtf-objdata-decoded RTF \objdata at offset 0x95C 21581 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 shell/COM execution token(s).
objdata_01_off0000b952.bin
0f2cec052fe8f824845b1aa6e0804ad719eb3010400f0023038dbc39515992c2
rtf-objdata-decoded RTF \objdata at offset 0xB952 2632 bytes
objdata_02_off0000cef5.bin
142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78
rtf-objdata-decoded RTF \objdata at offset 0xCEF5 12297 bytes