Malicious RTF — malware analysis report

Static analysis result for SHA-256 2f9099d5e261af71…

MALICIOUS

RTF

50.7 KB Created: 2017-08-02 10:25:00 First seen: 2017-08-08
MD5: 4631a2736434ad1c681728df24f151ff SHA-1: 2a5d0e5ca295219c08ce01be66a930a20189a742 SHA-256: 2f9099d5e261af71636db117f62c913e35bfca5c92cebb0c787f1818ea52ff3d
202 Risk Score

Malware Insights

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

The RTF file contains an OLE object that leverages CVE-2017-0199 to automatically link to and download a remote document from http://2.181.101.23:81/logo.doc. This exploit is commonly used to deliver secondary payloads, indicating a malicious intent to execute arbitrary code on the victim's machine. The presence of the OLE object and the specific CVE firing strongly suggest this attack pattern.

Heuristics 6

  • CVE-2017-0199 (OLE2Link / remote URL Moniker) critical CVE likely CVE_2017_0199
    RTF contains a URL Moniker OLE link whose decoded target is remote. Office can fetch and process the response through the CVE-2017-0199 OLE2Link attack path, but the server-side content type is not proven statically.
  • ClamAV: Rtf.Exploit.CVE_2017_0199-6335035-0 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Exploit.CVE_2017_0199-6335035-0
  • 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.
  • OLE object data medium RTF_OBJDATA
    RTF contains 1 \objdata section(s) — embedded OLE objects
  • OlePres presentation stream in RTF OLE object medium RTF_OLEPRES_STREAM
    RTF contains an embedded OLE object with an OlePres presentation stream. OlePres is an OLE presentation marker and is not enough on its own to identify CVE-2025-21298.
  • Embedded URL info EMBEDDED_URL
    One or more URLs were extracted from the document. The URL itself is not a detection — see the per-URL labels for which channel (macro, JS, link annotation, document body, ...) reached each URL.
    URL http://2.181.101.23:81/logo.doc In RTF body
    • http://schemas.microsoft.comIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002e30.bin rtf-objdata-decoded RTF \objdata at offset 0x2E30 4326 bytes
SHA-256: 45e6304307075066d2c80dd7cd5ae75e6f743c94410e2cd4df707c25a5c89347