Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 e2f73f4cf5b53c79…

MALICIOUS

RTF / .DOC

117.5 KB
MD5: 048a031d90b7a0144aff18781d491926 SHA-1: 2cd12d4dcc979ae6019c3203d6f7bcc52e00eb8c SHA-256: e2f73f4cf5b53c79aec72e02904ef216c11b755d6263d193141be3c317310127
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating a likely exploit for embedded objects. The \objupdate heuristic firing at offset 0x1D5CE is a strong indicator of malicious intent. The presence of Ole10Native stream further supports the embedding of executable content. No document body or script content was available for further analysis, limiting the ability to determine the exact payload or family.

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 1 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000003d.bin
d2fe9054346554bf961100e10351d51ddba22e477563ab9dfeba15519b1fcfcd
rtf-objdata-decoded RTF \objdata at offset 0x3D 3645 bytes