Malicious RTF / .DOC — malware analysis report

Static analysis result for SHA-256 ad04954e951c5327…

MALICIOUS

RTF / .DOC

21.4 KB
MD5: 694c298aea0a15abb3a929a2b65cae68 SHA-1: ba9922ea8e1ac51c179cab419c2134b36135e128 SHA-256: ad04954e951c5327c4d39f8b54de9f54951e6650965b6ecbdd5e1e839af52d34
100 Risk Score

Malware Insights

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

The sample is an RTF document containing OLE object data and ".objupdate" directives, indicating an attempt to exploit OLE activation. The high-severity heuristics RTF_OBJUPDATE and RTF_OLE10NATIVE_STREAM strongly suggest that embedded OLE objects are being used to trigger malicious code execution. The document body is heavily obfuscated and does not provide clear user-facing content, but the technical indicators point to a delivery mechanism for further malicious activity.

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_off00001b41.bin
57221f3f85d6290901bb3db9f9fca5180f71bafabb7324170e4d556760892298
rtf-objdata-decoded RTF \objdata at offset 0x1B41 3665 bytes