Malicious RTF — malware analysis report

Static analysis result for SHA-256 dba4aece8605ee17…

MALICIOUS

RTF

26.6 KB
MD5: 18dd40cd43c42c1fb35bea3f13b4056a SHA-1: bf7507cfd9583ba0f1cf98fd2b259343796e0f6c SHA-256: dba4aece8605ee17c1560428142fd548f00606ef0b4cdf73f9ceb320e829dfa9
100 Risk Score

Malware Insights

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

The RTF file contains OLE object data that is forced to activate via \objupdate, indicating an attempt to exploit OLE object handling. The presence of the Ole10Native stream further supports this. While no specific script was extracted, the heuristics strongly suggest the embedded OLE object is malicious and likely attempts to download and execute a secondary payload.

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_off00001fb5.bin
cf5a346ffbac87d87abda691ece8e40068f2320f9eb017efc3cbd7c484b4433b
rtf-objdata-decoded RTF \objdata at offset 0x1FB5 4181 bytes