RTF malware analysis — malicious · dfd507a747aa49b1

MALICIOUS

RTF

22.6 KB

MD5: 8a1a3caa1e0f138dc0d8016671682438 SHA-1: 6c2c4358fda4e243ee53d26311bdcf6898db8624 SHA-256: dfd507a747aa49b13351f35e97dde23519e56fb017dc2c5c0b60c1923511763e

100 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1059.001 PowerShell T1204.002 Malicious File

The RTF file contains OLE object data and triggers OLE activation via \objupdate, indicating it's designed to exploit OLE vulnerabilities. The embedded OLE object's native stream was decoded and found to contain executable content. No document body text or scripts were extracted, but the heuristics strongly suggest the file is a malicious OLE dropper. The SHA256 hash is included as a primary IOC.

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_off00000d96.bin` `5f59a9ce2254a356c78652798103913f107944c99f3eddb67c179a36cf51f138`	rtf-objdata-decoded	RTF \objdata at offset 0xD96	4183 bytes

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