RTF malware analysis — malicious · d582d45385eb1e9a

MALICIOUS

RTF

17.4 KB First seen: 2018-10-07

MD5: 2759f5542515d0d80785088720092ffb SHA-1: 26c9d0984ebb71a0f6211f83b3680fe7a9747e4f SHA-256: d582d45385eb1e9ac9a0a9bd7bc7f0ed4924122f97f188954781d1e4aa73f6ed

100 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF file contains embedded OLE object data that is forced to activate via \objupdate. This suggests the file is designed to exploit vulnerabilities or execute embedded code upon opening. While no specific script was extracted, the OLE activation strongly implies a mechanism for downloading and executing a second-stage payload, likely initiated by a spearphishing attachment. The lack of explicit script content prevents a higher confidence score.

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_off00000ed7.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xED7	4654 bytes
SHA-256: `0daf05b4675ea8258c6a2fa4a566e6102791e80ec5e4e250a28be4edccb38870`

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