Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 59de39d60fee5b2a…

MALICIOUS

RTF / .DOC

190.8 KB
MD5: a51beb4cee3604bc8ab1c7c9f5e7d5c1 SHA-1: 22d24e750b96783e24da802dcac3e4367d83befa SHA-256: 59de39d60fee5b2a853c4e4bd62ce6ea5054373938b8afbb159d60102f88e989
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects that are triggered for activation via \objupdate. This indicates an attempt to exploit OLE object handling to execute arbitrary code. The specific nature of the embedded object is not fully discernible from the provided heuristics, but the presence of \objdata and \objupdate strongly suggests a malicious intent to leverage OLE for code execution, likely as a downloader or initial execution vector.

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_off000007f0.bin
b5cfda8054229cc06b0214601181ba1ad89a97401c89536bd8a7ea48293598e8
rtf-objdata-decoded RTF \objdata at offset 0x7F0 3669 bytes