Malicious RTF — malware analysis report

Static analysis result for SHA-256 635b4ab69ed85f1f…

MALICIOUS

RTF

26.0 KB
MD5: 909896ca9cc9a93bae8a4424756853a0 SHA-1: 9f7f6a9450c3139e2254fe451a17b6e0589c1dd9 SHA-256: 635b4ab69ed85f1f6d52f3f28af550f090490e22ad13ea9aca3a018545521c43
100 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to execute embedded code. The decoded OLE object, identified as OLE10NAtIvE, suggests the potential for arbitrary code execution. While no specific family is identifiable, the technique strongly points towards a malicious document designed to exploit OLE vulnerabilities for initial execution.

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_off00001ab6.bin
53dd0b11310e3a999bafa4f3eb67fff97341322f135de87c8f90caa17c67173b
rtf-objdata-decoded RTF \objdata at offset 0x1AB6 4211 bytes