Malicious RTF — malware analysis report

Static analysis result for SHA-256 8da6c17dfbf7c241…

MALICIOUS

RTF

23.3 KB First seen: 2023-03-16
MD5: 2c83be7df56e4a884cddce5e8cc8f77c SHA-1: 4ad6116ecbc2e5f953a7d1ba106ba416d677b70b SHA-256: 8da6c17dfbf7c2414b4d2c72b23b7242b07feec00e7a1e896408a4b25fac3315
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data that is forced to activate via \objupdate, indicating an attempt to exploit OLE object handling. The presence of the Ole10Native stream further supports the embedding of executable content. This mechanism is commonly used to deliver and execute secondary payloads, likely leading to a broader infection chain.

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_off00001c36.bin
1a60309f6cab4e1485da66bc9a3c9df59d9b0e5c6240411f6ffc5f6c152c659c
rtf-objdata-decoded RTF \objdata at offset 0x1C36 3680 bytes