Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 558269dca96917e3…

MALICIOUS

RTF / .DOC

2.47 MB
MD5: 9f7b9edbacd4b26446a0b8c82c6edf6e SHA-1: a67c26f3f2306d9d02a9aede7d3e7b35ad1a437d SHA-256: 558269dca96917e3e5c81e8e97bde71b98bd081a56d43b5a003b9e36a335c860
140 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects with large amounts of hex-encoded data, indicated by RTF_EXCESSIVE_HEX and RTF_OLE10NATIVE_STREAM heuristics. The ".objupdate" directive suggests that these embedded objects are intended to be activated, likely to execute a hidden payload. The presence of the objdata_00_off000000fa.bin artifact further supports the delivery of a secondary payload.

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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~2529KB of hex-encoded data inside \objdata sections — may hide a payload
  • 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_off000000fa.bin
a9dced1be3a8ae8ec902a56476bd729e6bdd614866b7cc83fa887eb00e3a5e72
rtf-objdata-decoded RTF \objdata at offset 0xFA 1024703 bytes