Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 32d1ed4d0d689e2f…

MALICIOUS

RTF / .DOC

94.5 KB
MD5: 264ecec4fae4c5095f470746725ad860 SHA-1: f9231071445c3c835f3834c029924f8a70113983 SHA-256: 32d1ed4d0d689e2f7a6a897c95b1dfdc9c0f4dc6db406ae029a6e24011dba053
102 Risk Score

Malware Insights

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

The RTF document contains OLE object data that is automatically linked and updated, indicating an attempt to exploit OLE object activation. This suggests the document is designed to deliver a payload when opened. No specific family could be identified, and no further IOCs were extracted.

Heuristics 4

  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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 1 \objdata section(s) — embedded OLE objects
  • Suspicious extracted artifact info 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 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000005b.bin
a8da31e16a671a381adc14a74e0fe44b6635f9454edaaad24dfc4e93eb4bf9f1
rtf-objdata-decoded RTF \objdata at offset 0x5B 48178 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 7.99, consistent with packed or encrypted content.