Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 5ed29e3ddd922ee8…

MALICIOUS

RTF / .DOC

23.3 KB First seen: 2022-08-01
MD5: a7a0994f30b5d0df9bef8ffcc9854c60 SHA-1: 8eb2328dd553ead328157c9eb9ff0c6aebc47033 SHA-256: 5ed29e3ddd922ee865dc0c96484f93f247cf848d21304aae239499eeccba500f
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to exploit vulnerabilities related to embedded objects. The Ole10Native stream further suggests the presence of a malicious embedded object. These heuristics strongly point towards an exploit delivery mechanism.

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_off0000174a.bin
200f2fc01ace060c277b3b937a5984fbb6e01cfa4343a33e01e3d4dfe94f510b
rtf-objdata-decoded RTF \objdata at offset 0x174A 4316 bytes