Malicious RTF — malware analysis report

Static analysis result for SHA-256 745e935f75c9b2e5…

MALICIOUS

RTF

25.6 KB First seen: 2023-04-17
MD5: a970b581eee3770b96cc999859e82e9c SHA-1: cd92cb90883c8fe8058085fca270b0934eab65a6 SHA-256: 745e935f75c9b2e562c01bc04020b4f70dc2960fc3769037f8031136343ce8a0
100 Risk Score

Malware Insights

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

The RTF file contains embedded OLE objects, indicated by the RTF_OBJDATA heuristic. The RTF_OBJUPDATE heuristic suggests that the embedded object is designed to be activated automatically, likely to execute a malicious payload. The RTF_OLE10NATIVE_STREAM heuristic further confirms the presence of a decoded OLE object, which is a common technique for delivering malware. The document body is heavily obfuscated and does not provide clear textual lures.

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_off00001403.bin
6722105472f25fd5b60583d1f19be0e5b84a9a949640279a0a53b21685be6f16
rtf-objdata-decoded RTF \objdata at offset 0x1403 4173 bytes