Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 efaae724b6da0448…

MALICIOUS

RTF / .DOC

3.6 KB
MD5: b0cb595bbb76af1afd1ac4cba6f4805c SHA-1: 0732d3e7112e4117a579206263a2e047cc9e084a SHA-256: efaae724b6da044831fe1c797822f454dbca48a8b7c692d0b7fd25610475aac9
100 Risk Score

Malware Insights

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

The sample is an RTF document that contains OLE object data and is configured to automatically update and activate the embedded object. This indicates a likely exploit attempt to execute arbitrary code. The presence of `RTF_OBJDATA`, `RTF_OBJAUTLINK`, and `RTF_OBJUPDATE` heuristics strongly suggests the document is designed to leverage OLE object vulnerabilities for malicious purposes, such as downloading and executing a second-stage payload. No document body text or scripts were extracted, limiting further analysis of the specific lure or payload.

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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00000045.bin
3d2ec6fe6a4feefa6107ed4bb061e41b8d3b3455af5debf5cc93bcfb231a0289
rtf-objdata-decoded RTF \objdata at offset 0x45 1743 bytes