Malicious RTF — malware analysis report

Static analysis result for SHA-256 54613b979e2a83d3…

MALICIOUS

RTF

23.3 KB
MD5: f336f99018a0ec5c3b89af1295221c76 SHA-1: 95e93dea3bcedf4933e1bd291cce6719ce2276ce SHA-256: 54613b979e2a83d31933dcec33d1cb8316aab5bd1662a02080714c93b62e9ff8
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to execute embedded content. The high entropy of the decoded OLE object suggests it is likely packed or encrypted. No document body or scripts were extracted, limiting further analysis of the specific payload.

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_off000019c4.bin
b8e807a70f24880bb37033ac195d05c7bf8f91d91dfb21efaad6f33b49d891b1
rtf-objdata-decoded RTF \objdata at offset 0x19C4 4165 bytes