Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 2cb755b44a07942f…

MALICIOUS

RTF / .DOC

22.2 KB First seen: 2023-02-22
MD5: d48b33a8ccf7498c3fe3acda4f2f82f1 SHA-1: c64d8d3133c488396369bdb565ed68157f829195 SHA-256: 2cb755b44a07942f62c8e695520b7a2e23811430111527ba3c54eaf6cfeac013
100 Risk Score

Malware Insights

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

The RTF document contains an embedded OLE object, indicated by the RTF_OBJDATA heuristic. The RTF_OBJUPDATE heuristic suggests that this object is designed to be activated automatically, likely exploiting a vulnerability. The RTF_OLE10NATIVE_STREAM heuristic further confirms the presence of a decoded OLE object, which is the typical mechanism for delivering malicious payloads in such documents.

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_off000016ef.bin
d84c339133622e6f1231c12767f24f49eeb155585fea8d12ebd29aac5ac49aa6
rtf-objdata-decoded RTF \objdata at offset 0x16EF 3661 bytes