Malicious RTF — malware analysis report

Static analysis result for SHA-256 5c70a7edff808a2f…

MALICIOUS

RTF

112.9 KB First seen: 2026-02-04
MD5: 7e94fbb8330f2a994eb2f707aac45c14 SHA-1: 1a016becbfbfe9d4a8cc28511c096942b415bbe7 SHA-256: 5c70a7edff808a2fc109f26ebffc728cb39a3b28eb492417302167292f83dc44
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data that is forced to activate via \objupdate, indicating an attempt to execute embedded content. The Ole10Native stream further confirms the presence of a decoded OLE object. This suggests the file is designed to exploit OLE vulnerabilities for client execution, likely delivered as a spearphishing attachment.

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_off0000202c.bin
e255ce4ad76feba1995fd095b534240af909710b322c61c397eb63dc789397e3
rtf-objdata-decoded RTF \objdata at offset 0x202C 4178 bytes