RTF malware analysis — malicious · 20347a8a53e7c520

MALICIOUS

RTF

3.02 MB

MD5: a1f2f3c1c8ee34e79fbc179ee78e2574 SHA-1: c8f109013226d9f48bc1dad110f9cc91b7af8720 SHA-256: 20347a8a53e7c520c0e46c8862cc2538ba2a6a5edc9cc7746914b00992f1d3ca

160 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF document contains multiple heuristics indicating embedded OLE objects, with specific rules firing for OLE object data, embedding, and forced activation via \objupdate. A large amount of hex-encoded data within these objects suggests a hidden payload. The presence of the Ole10Native stream further supports the likelihood of an embedded executable or script designed to be launched upon opening.

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 ~3165KB 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.

Filename	Kind	Source	Size
`objdata_00_off000000c4.bin` `7c267436afe5667b0bf41c2354bf1060ebe017da1e08e95fcd08d563ec989cd7`	rtf-objdata-decoded	RTF \objdata at offset 0xC4	1055805 bytes

Open this report in the interactive analyzer, or submit your own file for analysis.