Malicious RTF — malware analysis report

Static analysis result for SHA-256 a097903243cbc6d2…

MALICIOUS

RTF

20.1 KB
MD5: 59efb49438295ee8736f72f126d94ed5 SHA-1: e1bac616ea8eca78889220ea612138f6688fb46b SHA-256: a097903243cbc6d2bd370031d764362b7e9214cc2d8fdb5c709e3b2122b7c3ac
100 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects, indicated by the RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that these objects are designed to be automatically activated upon opening the document. This technique is commonly used to deliver malicious payloads, often by exploiting vulnerabilities or tricking the user into executing embedded code. No specific family could be identified, but the attack pattern is consistent with a malicious document designed for initial compromise.

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_off00000d5d.bin
8433619beb093b2be209ba9e530d79d15a4c27338d8047b548195e7e0c8bcd59
rtf-objdata-decoded RTF \objdata at offset 0xD5D 3649 bytes