RTF malware analysis — malicious · 3f8fa4bb9c8c8b6f

MALICIOUS

RTF

48.4 KB First seen: 2018-08-14

MD5: 621cfae4eb73cad664fb8b97676bfc6c SHA-1: 68a53cd7636860b10ee4508f044447052b2778ef SHA-256: 3f8fa4bb9c8c8b6f4b2b2b3369741f89e1206ba061f7539faeccc58a61957947

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	12322 bytes
SHA-256: `74a6422c4538f3b3fb204f7605fc29ec47b2a48b4c5e842042779774a7e6e25a`

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