Malicious RTF — malware analysis report

Static analysis result for SHA-256 b436d0a34f9de9ba…

MALICIOUS

RTF

46.0 KB Created: 2018-11-19 22:50:00 First seen: 2019-05-10
MD5: 48fbcadc9804ce1b0d5959f013e17260 SHA-1: b602a4a9e5fa8c52593b308a015fce10f4874b9d SHA-256: b436d0a34f9de9ba0cf1e418c23c85f05ae64de801f176084a5184a895ad5f5a
182 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, a known vulnerability for remote code execution. The exploit attempts to download a secondary payload from the URL http://192.168.14.1/exploit.html. This indicates a likely attack pattern involving spearphishing, where the document serves as a lure to trigger the exploit.

Heuristics 5

  • 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
  • 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.14.1/exploit.html 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_off00002763.bin rtf-objdata-decoded RTF \objdata at offset 0x2763 2724 bytes
SHA-256: 6ed0349460e6702e91fec7b67c5c3a48997d061ed39bf909a06c460eac045e14