Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ba2443b047682add…

MALICIOUS

RTF / .DOC

235.6 KB First seen: 2022-07-11
MD5: 7a229870a7b9e7ed8ee70bf776abd043 SHA-1: 37c0cf062215ebe513ccbdc4344e3602bc6c097b SHA-256: ba2443b047682add81c516aff63a48dfbd505a5c3da24d9744cf1c71e9977c22
220 Risk Score

Malware Insights

MITRE ATT&CK
T1204.002 Malicious File: User Execution T1059.005 PowerShell

The RTF document contains OLE object data and triggers heuristics related to CVE-2017-8570, indicating it attempts to drop and execute a script. The document body explicitly instructs the user to 'Enable Editing', a common lure to bypass macro security. The embedded OLE object data, specifically the composite moniker, is a known technique for executing arbitrary code.

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_off00000ba4.bin
213b0475e2d275dae25e75038958d2ac64a9338eff9451cdf565eadbcce7d5a1
rtf-objdata-decoded RTF \objdata at offset 0xBA4 24151 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact contains 1 shell/COM execution token(s).
objdata_01_off0000d07c.bin
81ac98515bd4de25fc9f4148c41d6c0b489643c09de1fbb1e6bb969a785f1b01
rtf-objdata-decoded RTF \objdata at offset 0xD07C 2632 bytes
objdata_02_off0000e61f.bin
142dc43284d9abe994719f8fb67bc4c04bfc3f07528a1a66b0bad7e552ee8e78
rtf-objdata-decoded RTF \objdata at offset 0xE61F 12297 bytes