Malicious RTF — malware analysis report

Static analysis result for SHA-256 fbfbc6e81fb48d1e…

MALICIOUS

RTF

25.9 KB
MD5: 95b2667f1a1f47ebb18aeccc1a229443 SHA-1: 2fdad2a2827625f6ba6ba061b740d32f70f5ea2a SHA-256: fbfbc6e81fb48d1ee2de7dd6ca830b58f5f5f9c41468052c730222db6bdac7ac
120 Risk Score

Malware Insights

MITRE ATT&CK
T1566.002 Spearphishing Attachment T1204.002 Malicious File T1137.003 Libary Installation

The RTF file contains multiple OLE objects, with specific heuristics indicating that \objupdate forces OLE activation and that an Ole10Native stream is present within an embedded OLE object. This suggests the document is designed to exploit OLE object vulnerabilities to execute arbitrary code. No document body or script content was available for further analysis, limiting the ability to determine the exact payload or delivery mechanism.

Heuristics 4

  • 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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001cc7.bin
b03129e654bda8e5c44600e000bef09213fae5e3c7b7e517cc13c00100421743
rtf-objdata-decoded RTF \objdata at offset 0x1CC7 4185 bytes