Malicious RTF — malware analysis report

Static analysis result for SHA-256 5051a25b75ff32b5…

MALICIOUS

RTF

27.0 KB
MD5: c3d12616fa86608c82def10c1cb58d9e SHA-1: a2e8844ff494b5839a91c94e8d92e8e63cf92ac0 SHA-256: 5051a25b75ff32b562f56f5c138de98a3fc4d301ce6b2b7a7d6333faebab6936
140 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 that are configured for automatic updates and activation. This suggests an attempt to exploit OLE vulnerabilities or trick the user into activating the embedded object, which likely leads to the execution of a secondary payload. The heuristics indicate the presence of OLE object data and automatic linking, pointing towards a delivery mechanism that leverages these features to initiate malicious activity.

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_off00001f6c.bin
51d319789dfad14e02b477babd068d6282438d19ed8d23fe092de8f3affc54da
rtf-objdata-decoded RTF \objdata at offset 0x1F6C 4173 bytes