Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 32c9e90e2cf72e2d…

MALICIOUS

RTF / .DOC

164.9 KB
MD5: d87b7d6a8a6e8e14862a3b86b83c86fb SHA-1: 3bb19190fd9e216a4d9876252b51ad33a187b2b6 SHA-256: 32c9e90e2cf72e2da62927932d952513ad1e6c1d2b0ba606a200e03cd06f9cc9
102 Risk Score

Malware Insights

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

The RTF document contains OLE object data and is configured to automatically update and activate these objects. This suggests an attempt to exploit vulnerabilities associated with OLE object handling to deliver a malicious payload. The presence of an extracted OLE object further supports this. Without further script or URL evidence, the exact nature of the payload remains undetermined.

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_off0000005f.bin
20983d7dd5e50ff354bd923a257403b0b46a13530d413b6e5055475019a507d7
rtf-objdata-decoded RTF \objdata at offset 0x5F 84287 bytes
Detection
ClamAV: No threats found
Obfuscation or payload: likely
Carved artifact entropy is 8.00, consistent with packed or encrypted content.