Malicious RTF — malware analysis report

Static analysis result for SHA-256 e35109a09ab67309…

MALICIOUS

RTF

180.3 KB First seen: 2024-07-04
MD5: 2065f134f20986527b4023d59e12081c SHA-1: 3a103cafe7d928c66d00bd07830a864f549dccd4 SHA-256: e35109a09ab67309cdd6455d92bca6f2b67a11791cfc1df8008289f0b2a8963f
100 Risk Score

Malware Insights

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

The sample is an RTF file exhibiting high-confidence heuristics for OLE object activation and embedded data. The RTF_OBJUPDATE heuristic indicates that the document forces OLE activation, which is a common technique for executing embedded malicious content. The presence of OLE object data and the Ole10Native stream further support this. The document body is heavily obfuscated and does not provide clear textual lures, but the technical indicators strongly suggest a malicious payload is being delivered via OLE object exploitation.

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_off00001d68.bin
314cd1007fa1424f36ee14983df153993d2c6e4ad5078f431570f45ee69fda7a
rtf-objdata-decoded RTF \objdata at offset 0x1D68 4182 bytes