Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 0593e35d01569ad3…

MALICIOUS

RTF / .DOC

253.4 KB
MD5: 17b4006f53c6f1f98d773985fed111ca SHA-1: bd91bcb400112ce8baa4d664d82d40684111f0bd SHA-256: 0593e35d01569ad38e6ed1ca46305ba9cd1dc93ac6a1beb9ce104f919baf23ff
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force activation, indicating an attempt to execute embedded content. The presence of the Ole10Native stream further supports this. While the exact payload is not visible, the heuristics strongly suggest exploitation for client execution, likely delivered via spearphishing.

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_off00001d01.bin
f9d8a1540236e604ca88d4ce306b539626ee278e391efd1ea17cb576b6994740
rtf-objdata-decoded RTF \objdata at offset 0x1D01 4164 bytes