Malicious RTF — malware analysis report

Static analysis result for SHA-256 468a9f796f26c5cd…

MALICIOUS

RTF

25.3 KB First seen: 2023-05-08
MD5: bdff5c8782a221578cb25c9a8c076ff3 SHA-1: 21bec8c9c3821da3735b03d8f6d48c78410cf490 SHA-256: 468a9f796f26c5cdf195a0fecce2c5cb96cc9dde10ee9ed542af0209eade1411
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data and uses \objupdate to force OLE activation, indicating a likely exploit attempt. The presence of an Ole10Native stream further supports this. While no specific document body content or scripts were extracted for direct analysis of user-facing lures, the RTF structure strongly suggests a malicious payload delivery mechanism, likely involving embedded exploits.

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_off00001c51.bin
7da61a17248e01993c87737780fce4828f863bfd1452f8e8315ebdfe875b3264
rtf-objdata-decoded RTF \objdata at offset 0x1C51 3660 bytes