RTF malware analysis — malicious · 4c48e475dd37f0c8

MALICIOUS

RTF

1.07 MB First seen: 2018-05-18

MD5: aded255f4ffc2b2d73600d3289d39bf0 SHA-1: 2c9e1f28342962f914680fe4a01379d2a17c36d8 SHA-256: 4c48e475dd37f0c80aedf43513f61b7d767b001d069dfbc3b4beb8dfd4461e3f

140 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment

The RTF file contains OLE object data with a high degree of hex-encoded data, indicating a potential payload. The presence of \objupdate suggests an attempt to force OLE activation. While no scripts were directly extracted, the structure strongly implies the embedded OLE object is malicious and likely intended to execute a secondary payload, possibly via a technique like T1059.007 if it contains script-like content, or T1566.001 as a spearphishing attachment.

Heuristics 4

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 ~1087KB of hex-encoded data inside \objdata sections — may hide a payload
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_off00001185.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x1185	27656 bytes
SHA-256: `d5758ea8bbfd100b4844335fbb79a374f8813176bb44f254903b29f1cc0944c2`

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