RTF malware analysis — malicious · f514cf657d0c5c62

MALICIOUS

RTF

10.0 KB First seen: 2017-12-24

MD5: 3bcb7fca490b7ce0aaf6a14b6bfdf811 SHA-1: b75f995342046bed66b2dd1a4f283575022cfc23 SHA-256: f514cf657d0c5c629e5bfea5555094fb1d29ff02ad714264a3248f86b7eb7140

140 Risk Score

Malware Insights

MITRE ATT&CK

T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF file contains embedded OLE objects that are configured for automatic updates, indicating an attempt to exploit vulnerabilities for client execution. The presence of URL monikers strongly suggests that the embedded object is designed to download and execute a secondary payload from a remote location. While no specific script was extracted, the RTF structure and OLE object behavior point towards a common malware delivery pattern.

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_off0000003e.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x3E	4099 bytes
SHA-256: `555237cde40f8b2e59f0075618d6d1a98295b4e0a4aee4865593a74b72d87731`

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