Malicious RTF — malware analysis report

Static analysis result for SHA-256 ccfd36787a214671…

MALICIOUS

RTF

88.2 KB First seen: 2025-06-24
MD5: 1789e0570d65f05981c8a164c35cac9b SHA-1: 011e7212e935f8ab5d874021000422d9de3c7e1c SHA-256: ccfd36787a2146715e5907820c2d5f05dd32c4e4c7151e53683fea0724dff70a
100 Risk Score

Malware Insights

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

The sample is an RTF document containing OLE object data and ".objupdate" directives, indicating an attempt to exploit OLE activation mechanisms. This suggests the file is designed to trick the user into opening it, which then triggers the execution of embedded malicious content. The specific OLE object stream identified as 'oLE10naTIVe' further supports this attack vector. No scripts were extracted, and the document body was heavily obfuscated and truncated, preventing a more detailed analysis of the lure.

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_off00001ea8.bin
2612c51a4abffd0cd63cdc422469117e288027016e4ae4834f8e1753721d6aef
rtf-objdata-decoded RTF \objdata at offset 0x1EA8 4736 bytes