Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 0d91d92b0ba0d54b…

MALICIOUS

RTF / .DOC

252.2 KB
MD5: de23a2267336aa69d9daefd9f7d0c423 SHA-1: 479fa176561cb85fefee00cf89f348927d77147a SHA-256: 0d91d92b0ba0d54bec25ee86351a43ad77f2692697a6ddda6cc427c497d12251
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF document contains embedded OLE object data and uses \objupdate to force activation, indicating an attempt to exploit vulnerabilities for client execution. The presence of RTF_OLE10NATIVE_STREAM further supports the embedding of executable content. While no specific script was directly extracted, the structure suggests the OLE object likely contains or leads to a payload, possibly a JavaScript downloader, hence the inclusion of T1059.007.

Heuristics 3

  • Ole10Native stream in RTF OLE object high CVE related RTF_OLE10NATIVE_STREAM
    RTF contains an embedded OLE object with an Ole10Native stream. This is a strong payload-container signal and is related to Word/OLE exploit delivery, but it is not specific enough on its own to assign a CVE.
  • \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_off000019fb.bin
722f8fe6de94c7848e019e6f65896d5a2368c03b1b9149e613ecf8ec4549a38c
rtf-objdata-decoded RTF \objdata at offset 0x19FB 4174 bytes