Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 679fca0a3e4f112b…

MALICIOUS

RTF / .DOC

253.5 KB
MD5: f977140ed2efb487abbee562a4daaa1b SHA-1: 52244825e7309d22dd28e1d870a5154e1de017bc SHA-256: 679fca0a3e4f112bfbe5debef5916bfe7ebaef8e64f058c2fab897b7c0d83c0b
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data that is triggered for activation via \objupdate, indicating an attempt to execute embedded content. This is a common technique for delivering secondary payloads. While no specific family is identified, the method strongly suggests a malicious document designed for initial compromise.

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_off00001bb8.bin
65f3da5365bd6a05b49017f9a846c4406dee5901205b7202fdf6614620eb3723
rtf-objdata-decoded RTF \objdata at offset 0x1BB8 4182 bytes