Malicious RTF — malware analysis report

Static analysis result for SHA-256 5f6cbdf15b147197…

MALICIOUS

RTF

30.7 KB First seen: 2019-04-18
MD5: 074d055caedc5522cd961089e913de70 SHA-1: 60c4c871594b2f8ba293aab2ac9eaba37add8198 SHA-256: 5f6cbdf15b147197418e2a24b1886d106dc506039176a05ed194963d2e75ca2f
140 Risk Score

Malware Insights

MITRE ATT&CK
T1566.001 Spearphishing Attachment T1203 Exploitation for Client Execution

The RTF file contains multiple high-severity heuristics indicating the presence of an OLE object with automatic linking and update capabilities. This suggests the file is designed to exploit vulnerabilities in OLE object handling to execute arbitrary code. The embedded URL, though heavily obfuscated, is likely the source of a secondary payload.

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.

FilenameKindSourceSize
objdata_00_off0000546a.bin rtf-objdata-decoded RTF \objdata at offset 0x546A 3304 bytes
SHA-256: 070e20a54d8cb351d99192f38f7563256125d45a74c90c6dc8859c02359b5e86