Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 b695826ebfd171dd…

MALICIOUS

RTF / .DOC

15.7 KB
MD5: aec5ece74af68b45745edee134a66d5b SHA-1: e2c791e52160c76e9ff4b0074b46b52222c6b392 SHA-256: b695826ebfd171ddc5a1d86d2841daeada46702cfa0dff52ed03701d95d70076
100 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, indicated by the RTF_OBJDATA heuristic. Furthermore, the RTF_OBJAUTLINK and RTF_OBJUPDATE heuristics suggest that these embedded objects are automatically linked and their activation is forced. This points to a likely attack pattern where the document attempts to exploit OLE object vulnerabilities or trick the user into activating embedded malicious content, potentially leading to further stages of infection. No specific malware family could be identified.

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_off00001396.bin
37c97c8382b9300a8481822a5831b492b6eb3be801b0dd5e2912c85b3d0b9686
rtf-objdata-decoded RTF \objdata at offset 0x1396 1799 bytes