RTF malware analysis — malicious · 141fe8ed9b91ccfc

MALICIOUS

RTF

8.7 KB First seen: 2017-12-24

MD5: d380038266b4e756a8ce7561defaeed3 SHA-1: 7cb57b059b1ba434cff24160a2f668d4cfbd59a6 SHA-256: 141fe8ed9b91ccfc035625994f066e701b4617372c48bf66cca4603cf3b6fd75

140 Risk Score

Malware Insights

MITRE ATT&CK

T1203 Exploitation for Client Execution T1566.001 Spearphishing Attachment

The RTF file contains OLE object data with automatic linking and update triggers, indicating an attempt to execute embedded content. The presence of a URL Moniker strongly suggests that the OLE object is designed to download and execute a second-stage payload from a remote location. This technique is commonly used to deliver malware via email attachments.

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_off0000003f.bin`	rtf-objdata-decoded	RTF \objdata at offset 0x3F	4298 bytes
SHA-256: `f3b61880fed7a02bf9ad3e026648584a6a696819592593f8ef63fe42c2666200`

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