Malicious RTF — malware analysis report

Static analysis result for SHA-256 04e997a4fddfc2d6…

MALICIOUS

RTF

5.6 KB First seen: 2017-10-10
MD5: b9d4c0aa5df920ff64c6bdc194426140 SHA-1: d645b1652f9614e070ce182986d1c850054ece28 SHA-256: 04e997a4fddfc2d65416366d766e57ab87071a209f77a236a7166b4e9887f0b5
222 Risk Score

Malware Insights

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

The RTF file contains an OLE object that is automatically linked and updated, exploiting CVE-2017-0199. This exploit is designed to download and execute a secondary payload, in this case, a HTA file from the IP address 192.168.1.66. The embedded URL is the primary indicator of compromise.

Heuristics 6

  • 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.
  • 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.
  • \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://192.168.1.66:4444/default.hta 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_off000001b4.bin rtf-objdata-decoded RTF \objdata at offset 0x1B4 2601 bytes
SHA-256: afcc7ccd148508bfa8839c00ebfcf4bc061ed4d486146c598c204fd6f5eb5daf