Malicious RTF — malware analysis report

Static analysis result for SHA-256 980d161c1a8863bf…

MALICIOUS

RTF

24.7 KB First seen: 2023-06-10
MD5: 282f3b518b202b031c75151ab99761a7 SHA-1: 7d9a57456adfe95f1523eb0ec3b4b35495008544 SHA-256: 980d161c1a8863bf446d89848051f8af7f8eccc22f5173c11a1d461f83b24edc
100 Risk Score

Malware Insights

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

The RTF document contains OLE object data that is forced to activate via \objupdate, indicating an attempt to exploit OLE vulnerabilities. The presence of the Ole10Native stream further supports the embedding of executable content. While no specific scripts or URLs were extracted, the heuristics strongly suggest a malicious OLE object designed to execute a payload.

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_off00001b16.bin
98f58df2d78914ca462dc34974e2ba1940b451cd16174558a182c4824ced29d7
rtf-objdata-decoded RTF \objdata at offset 0x1B16 3654 bytes