Malicious RTF — malware analysis report

Static analysis result for SHA-256 df5250f5c309c55c…

MALICIOUS

RTF

23.8 KB
MD5: 101432a1a18a5696344be741f620349b SHA-1: 36bac688d43e4c924d02c9f15580bcb9f70bb80f SHA-256: df5250f5c309c55ca165ac4300ebf6fc63dd4988c01e73bd3e50cb7753c34d4f
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to exploit embedded objects. The presence of the Ole10Native stream further supports this. While no specific script was extracted, the heuristics strongly suggest the document is designed to trigger malicious code execution via OLE object manipulation, likely as a delivery mechanism for further payloads.

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

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001455.bin
d260fb8ad9578113a60013a66752698e500ddb353e0103eb3e5fb4109180b329
rtf-objdata-decoded RTF \objdata at offset 0x1455 4190 bytes