RTF malware analysis — malicious · 8ab005d33f09bcae

MALICIOUS

RTF

30.6 KB First seen: 2019-08-04

MD5: 043ac190a716432086c4ff6aefff7af7 SHA-1: 9c1f970bf296151c362b118a02a00dc85032870c SHA-256: 8ab005d33f09bcae9a59b4b1292c6d7dcea2009b5793bf25347460d2e075bec3

140 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains high-severity heuristics indicating the presence of OLE objects that are automatically linked and updated. These objects likely contain a URL moniker designed to download and execute a secondary payload, a common technique for initial execution of malware. The specific URL is obfuscated but the presence of the moniker is a strong indicator of malicious intent.

Heuristics 4

URL Moniker in RTF OLE object high CVE related RTF_URL_MONIKER_RELATED

RTF contains a URL Moniker GUID in OLE object context, but no decoded remote target was confirmed. Treat as related OLE2Link attack-surface evidence rather than proof of CVE-2017-0199 exploitation.
Automatically linked OLE object high RTF_OBJAUTLINK

RTF contains \objautlink — an automatically linked OLE object surface that can be updated or activated when Word opens the document.
\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_off0000546a.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x546A	3306 bytes
SHA-256: `cbfe84ad313349157db883bc49a1c21e1dc6858c88d42aa1329aebc6e66957c6`

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