Malicious RTF — malware analysis report

Static analysis result for SHA-256 edea94d961e9e376…

MALICIOUS

RTF

6.1 KB First seen: 2017-11-20
MD5: 384eda73e72220ff9bf7bf31a8742caa SHA-1: ecc844c5ecb9b28fc93d9cdd1eeaee9cc7a9da5a SHA-256: edea94d961e9e376aad096a03e4c6ef51e2a8f878dbafbdc79fdab12923059a3
162 Risk Score

Malware Insights

MITRE ATT&CK
T1203 Exploitation for Client Execution

The RTF file contains an OLE object that is automatically linked and updated, exploiting CVE-2017-0199. This vulnerability is used to download and execute a secondary payload from the URL http://josephioseph.com/hswift.hta. The embedded OLE object data and the weaponized URL are strong indicators of malicious intent.

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.
  • \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
  • 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://josephioseph.com/hswift.hta In RTF body

Extracted artifacts 1

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off0000003e.bin rtf-objdata-decoded RTF \objdata at offset 0x3E 3110 bytes
SHA-256: a1dbe9335f2776e11f896a90526559794a48ca5ac764779b20b7fc7046f5f5de