RTF malware analysis — malicious · 65a324b29465be1e

MALICIOUS

RTF

21.8 KB

MD5: 8a25509caecbb8f37f4e98af64a70a65 SHA-1: 9d31b9d3fca3852275faef8dc827f41517c07388 SHA-256: 65a324b29465be1e595e6351f060c5b6b730b9425146c3b1acae85922d3df84b

100 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The sample is an RTF document containing OLE objects, indicated by the RTF_OBJDATA and RTF_OLE10NATIVE_STREAM heuristics. The RTF_OBJUPDATE heuristic suggests that these objects are designed to be automatically activated, which is a common technique for executing embedded malicious code. The specific OLE object data is extracted as 'objdata_00_off00000b6f.bin'. Given these findings, the most likely attack pattern is spearphishing attachment leading to exploitation for client execution.

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.

Filename	Kind	Source	Size
`objdata_00_off00000b6f.bin` `74cf1d14f36fbd854bb92c31e671b3320afbe8fabf4ec98a6d0518712e8d2b00`	rtf-objdata-decoded	RTF \objdata at offset 0xB6F	4179 bytes

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