Malicious RTF — malware analysis report

Static analysis result for SHA-256 dfba5870f97cb00e…

MALICIOUS

RTF

2.98 MB
MD5: a58c637416c0fca2c1bb23dc5c099fc0 SHA-1: de629b0ee92e4c7a10f57a59de0f0c3e5c9ac312 SHA-256: dfba5870f97cb00e7a602fe18fbdd69d9eddbe789b1e7dcf85d9d744fa8e540c
160 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF file contains multiple high-severity heuristic firings indicating the presence of embedded OLE objects with significant amounts of hex-encoded data, likely serving as a hidden payload. The \objupdate heuristic suggests that these objects are designed to be activated, leading to the execution of malicious code. Given the nature of RTF files and embedded objects, this is likely delivered as a spearphishing attachment.

Heuristics 5

  • 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.
  • Large hex data blocks in OLE object high RTF_EXCESSIVE_HEX
    RTF contains ~3124KB of hex-encoded data inside \objdata sections — may hide a payload
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \objdata section(s) — embedded OLE objects
  • Embedded OLE object medium RTF_OBJEMB
    RTF contains \objemb — embedded OLE object

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00001308.bin
cbc92dfae27d630a53f9019d680bb03a128c8909a91861b9f723b17eb7214b89
rtf-objdata-decoded RTF \objdata at offset 0x1308 1041988 bytes