Malicious RTF — malware analysis report

Static analysis result for SHA-256 f11ee6222bc510e8…

MALICIOUS

RTF

22.7 KB First seen: 2022-04-24
MD5: f4aada82e9e4f66b015b4de0765cfac4 SHA-1: 6540a96c84b2e7c931c843c92958782607a6bf81 SHA-256: f11ee6222bc510e8ccb2b73c44180915c013ec2af37bfa34825d8a82df48a7d9
121 Risk Score

Malware Insights

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

The RTF file contains OLE object data and uses \objupdate to force OLE activation, indicating an attempt to exploit embedded objects. The Ole10Native stream further confirms the presence of a decoded OLE object. While no specific script was extracted, the heuristics strongly suggest the file is designed to trigger malicious code execution via OLE object manipulation, likely as a lure for further payload delivery.

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 2 \objdata section(s) — embedded OLE objects

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001e56.bin
6fbb6f60cb37b4024053c895c84159c7c1373c5312ae00107b15f53f1abcd27a
rtf-objdata-decoded RTF \objdata at offset 0x1E56 3685 bytes