RTF malware analysis — malicious · 0b2bddc9b98d13be

MALICIOUS

RTF

19.6 KB First seen: 2022-09-21

MD5: 76f43de5cf847ba3151a8254c209017e SHA-1: 67ad1289e780047650596a41fd4cd72141728963 SHA-256: 0b2bddc9b98d13bebebbd5eaf0451ed80dd046b47fa3b5d0117fea66dbedbc39

100 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1204.002 Malicious File

The RTF file contains OLE object data and uses \objupdate to force activation, indicating an attempt to exploit OLE vulnerabilities. The embedded OLE object, decoded from the Ole10Native stream, likely contains the malicious payload. While no specific family is identified, the technique suggests a downloader or exploit delivery mechanism.

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.

Filename	Kind	Source	Size
`objdata_00_off00001b1c.bin` `28cc3f9853d68ec76b8f9e3f993353dcab04401047acc8465bf5c27ad078256a`	rtf-objdata-decoded	RTF \objdata at offset 0x1B1C	3678 bytes

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