Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 9e5581a99217d929…

MALICIOUS

RTF / .DOC

17.9 KB
MD5: 0d5477d7a2b13abeb64f8e6750aa3c09 SHA-1: 2c3a5ab784188c8ba2bd9091f4e894f647f314f7 SHA-256: 9e5581a99217d92957e04ecda2a2c591c869bcc8d0405b5ece66ed134e6b24e2
100 Risk Score

Malware Insights

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

The sample is an RTF document that leverages OLE object data and automatic linking, as indicated by the RTF_OBJDATA, RTF_OBJAUTLINK, and RTF_OBJUPDATE heuristic firings. These indicate that the document is designed to automatically activate embedded OLE objects when opened, which is a common technique for delivering malicious payloads. The specific nature of the payload is not detailed in the provided evidence, but the mechanism strongly suggests a phishing or credential harvesting attempt.

Heuristics 3

  • 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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001f56.bin
d983a28194b37819d0454691fc58d9663bbbd09212b7e5838639bd2e23f1ab5b
rtf-objdata-decoded RTF \objdata at offset 0x1F56 1650 bytes