RTF malware analysis — malicious · 8bc940a821582bc4

MALICIOUS

RTF

17.3 KB First seen: 2018-09-04

MD5: c6546c41115d28f73ced45f98f4cb142 SHA-1: f02b8871fa735d9fa447033628a0d7fc67b7a75e SHA-256: 8bc940a821582bc43c0fe87368715e3ba543fc4f757b14eff357d6ee61d9cce5

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_off00000ed9.bin`	rtf-objdata-decoded	RTF \objdata at offset 0xED9	4662 bytes
SHA-256: `58c4ba0300a3057cd87f9921f03946a156e2dbe49e46af895df49237f84dbde6`

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