Malicious RTF — malware analysis report

Static analysis result for SHA-256 7977b77c6c8969db…

MALICIOUS

RTF

5.6 KB First seen: 2018-03-04
MD5: ac8d1cc5e160c96b622266dc719793b3 SHA-1: 9169346b8e48155eb14cf23ec1cbafeac4f73283 SHA-256: 7977b77c6c8969db0bd13a40cd0d62da0aa934f00f5affcccc6a3501a0c4c853
222 Risk Score

Malware Insights

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

The RTF file contains embedded OLE object data that is automatically linked and updated, exploiting CVE-2017-0199. This vulnerability is used to fetch and execute a HTA payload from the specified URL. The ClamAV detection confirms the malicious nature of the exploit.

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.102:8080/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: 3f1f25886333d6407099a723d5c9eb69ee6aba5443714122d142fde742214955