Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 4ed43aa0c0ab7b05…

MALICIOUS

RTF / .DOC

329.8 KB
MD5: 8de3f790144bd3aa89553a8d7beda505 SHA-1: ba254e8e3fcd05443ce137bdc1bfd3da0299e805 SHA-256: 4ed43aa0c0ab7b05cf60c5532d107f30a21efdf9f8d917a07c73d3044494bc68
120 Risk Score

Malware Insights

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

The RTF document contains embedded OLE objects, with heuristics indicating that \objupdate forces OLE activation. This suggests the document is designed to exploit OLE vulnerabilities or trick the user into activating embedded content, likely to download and execute a secondary payload. The presence of OLE object data and embedding points to a common delivery mechanism for malware.

Heuristics 4

  • 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
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000008b3.bin
318e56481de7696925ecbec05f38bf9bc86936ec5a0ce746ea05ccb53d94ea68
rtf-objdata-decoded RTF \objdata at offset 0x8B3 101337 bytes