Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 284329f62fc4b356…

MALICIOUS

RTF / .DOC

227.1 KB
MD5: 01a0f0a36529d65a317abc215b8c18f9 SHA-1: e056f860025789ab2909f8e52e0c28b67babae0d SHA-256: 284329f62fc4b35697829279fec9a6d6e16a6cb01b5b7193c6093e723058594d
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating a likely exploit. The Ole10Native stream further suggests embedded malicious content. While no specific payload or URL was extracted, the heuristics strongly point to a malicious RTF file designed to exploit OLE vulnerabilities for code execution, commonly used for downloading further stages.

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_off0000068b.bin
b9c3f8b98c8629c0cff45af9bc10d93318e7cc49b21e6c3dc61212f6ab8ee939
rtf-objdata-decoded RTF \objdata at offset 0x68B 4176 bytes