Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 e9cb60234089cc8b…

MALICIOUS

RTF / .DOC

80.8 KB
MD5: dd93a4d457580aeb49e4f1284a530abb SHA-1: 0cda99376df7ce05c98f5398452f7f7c4e1847f0 SHA-256: e9cb60234089cc8b422cb51d1c12fe510d4e69deb300a55356c91108826453ba
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects that are triggered for activation via \objupdate. This indicates an attempt to exploit OLE object vulnerabilities to execute arbitrary code. The specific nature of the payload is not clear from the static analysis, but the technique strongly suggests a malicious intent, likely to download and execute a secondary payload or establish a foothold on the system. Confidence is moderate due to the lack of script content for definitive payload analysis.

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_off00001b25.bin
92407e855b53239f5f2fdb13c578b23b165f35ff73257a43eca84985e56888d7
rtf-objdata-decoded RTF \objdata at offset 0x1B25 4169 bytes