Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ce641eba2913ce51…

MALICIOUS

RTF / .DOC

23.2 KB First seen: 2022-08-10
MD5: 631a2183d691f90a758710e3a42f7e83 SHA-1: 5429e6f45aa92d9d2bc3d076a108c34750c285a5 SHA-256: ce641eba2913ce51e612fcd9ea4e11a32b7eb5d695041b29e7cb62bcd95f871b
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data and uses \objupdate to force activation, indicating an attempt to execute embedded content. The presence of OLE object data and the \objupdate heuristic strongly suggest a malicious OLE object is embedded within the RTF file. This is a common technique for delivering secondary payloads.

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_off00001e4a.bin
6f41a8153584d56ffbb55aefa213440ccc5cb5c6ef521c9966304489da52d744
rtf-objdata-decoded RTF \objdata at offset 0x1E4A 3792 bytes