Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 69e5d91520fb83cb…

MALICIOUS

RTF / .DOC

46.9 KB
MD5: 1d970b8fbb90fb304d18559de9916ac6 SHA-1: 7ed7e1917c3a00cb5291cc1881ee7677b1676fb7 SHA-256: 69e5d91520fb83cb0e9259ab2e8c418e7699357c2a61bfdc998c0a2f2cfe936c
100 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The sample is an RTF document containing OLE object data with an \objupdate directive, indicating an attempt to automatically activate embedded objects. This is a common technique for exploiting vulnerabilities or delivering malicious payloads. The presence of OLE object data and the \objupdate heuristic strongly suggest exploitation for client execution, likely delivered via a spearphishing attachment.

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_off00001e4e.bin
e0eb11e9dcfb854095d078dd32896fad31e558067778b3eaf3e04f614a7f9629
rtf-objdata-decoded RTF \objdata at offset 0x1E4E 4178 bytes