Malicious RTF — malware analysis report

Static analysis result for SHA-256 d84d50f6bab632f5…

MALICIOUS

RTF

25.9 KB
MD5: d96431380975c0c711acd8795b99fd76 SHA-1: 363bbac3475d982d0654e5e6ec67abb3aa5845fd SHA-256: d84d50f6bab632f52dc445025a63d8d5cfd537fefaf380cad2f6710b57939b14
140 Risk Score

Malware Insights

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

The RTF file contains OLE object data, automatically linked OLE objects, and triggers OLE activation via \objupdate. This suggests the file is designed to exploit OLE vulnerabilities to execute embedded malicious content. The presence of Ole10Native stream further indicates the embedding of executable content. The document body is heavily obfuscated and does not provide clear textual lures.

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.
  • Automatically linked OLE object high RTF_OBJAUTLINK
    RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
  • \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_off00001b05.bin
39fbd87dade27a838e23564f120fa2afbb2f58e53bfcd639a449124493d9ef71
rtf-objdata-decoded RTF \objdata at offset 0x1B05 4189 bytes