Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ca2acb0338f04853…

MALICIOUS

RTF / .DOC

20.6 KB First seen: 2022-11-28
MD5: 3eb05e04fa60047494f190f1f871c6fd SHA-1: 1c85e7f70e8d6503da9d2a86fd0cf7f2d8e06df9 SHA-256: ca2acb0338f04853d1e5e2a0c29ac3a3f6e4f5d2c8aba93a7fe4147c5b076123
100 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1204.002 Malicious File T1027 Obfuscated Files or Information

The RTF document contains embedded OLE object data and uses an \objupdate directive, indicating an attempt to automatically activate and execute the embedded object. This is a common technique for delivering malicious payloads, often through spearphishing attachments. The specific nature of the payload could not be determined due to the obfuscated nature of the embedded object.

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_off00000ed9.bin
bc95c0b82e8e0887afa9f61cec32946c9060fbd56b2507bf1f25a089f21bb20f
rtf-objdata-decoded RTF \objdata at offset 0xED9 4177 bytes