Malicious RTF — malware analysis report

Static analysis result for SHA-256 bf433e68ed5c635b…

MALICIOUS

RTF

251.2 KB First seen: 2024-12-03
MD5: 8ad51084a81ff40b5f8c55377d9311df SHA-1: 5304c07cad5f697c794c01bee1f26f5eb6d77ae2 SHA-256: bf433e68ed5c635b23fe449ef4ee47cfe774140d6f669f1a3f6e7e3b95f4b5a4
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to exploit embedded objects. The presence of \objupdate and Ole10Native stream strongly suggests a malicious OLE object is embedded, likely to execute arbitrary code upon opening. No document body or script content was available for further analysis, limiting the ability to determine the specific payload or delivery mechanism.

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_off00001c8d.bin
4115469e783c7f9f873fbef96fd2ce63783032bd334ff15732b9ead35900dffd
rtf-objdata-decoded RTF \objdata at offset 0x1C8D 4167 bytes