Malicious RTF — malware analysis report

Static analysis result for SHA-256 d141138cc56f541b…

MALICIOUS

RTF

621.8 KB Created: 2017-09-14 07:25:00 First seen: 2017-10-10
MD5: ed4b8cdfdd7e4161ae123c1375307395 SHA-1: b9df21ce5ed2d9054b5a1960aa4d31e144304ce0 SHA-256: d141138cc56f541b87e173d4da3551199b0b37e5bb87e7c945394dd7d6b86268
142 Risk Score

Malware Insights

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

The RTF file contains an OLE object that exploits CVE-2017-0199, indicated by the 'CVE_2017_0199_WEAPONIZED_URL' heuristic. This exploit is designed to download and execute a payload from the embedded FTP URL. The presence of OLE object data and an automatically linked OLE object further supports the exploitation vector.

Heuristics 5

  • CVE-2017-0199 (OLE2Link / weaponized URL) critical CVE exact CVE_2017_0199_WEAPONIZED_URL
    RTF contains a URL Moniker OLE link to a script/HTA/template-style remote loader, matching the tighter static CVE-2017-0199 shape.
  • 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://domain.com/uag.php In RTF body
    • http://schemas.microsoft.com/office/word/2003/wordmlIn RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off00002a5a.bin rtf-objdata-decoded RTF \objdata at offset 0x2A5A 4242 bytes
SHA-256: 697ca9824765426c5d0f089b6fe799d5366c65e6607d19df1c05038c3ddc5821