Malicious RTF — malware analysis report

Static analysis result for SHA-256 06983072430921d5…

MALICIOUS

RTF

50.1 KB Created: 2017-04-26 22:56:00 First seen: 2017-10-10
MD5: 6e3c3fd16df339a6c1022d8ff2990a0e SHA-1: 5cc31ae7ffa97235187881edee687b425fc1e2e6 SHA-256: 06983072430921d51a70f958984d77ac1da62b36ddeeaf894d5a420a6fc3bc23
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 targets the URL http://127.0.0.1/applications.html to download and execute a secondary payload. This indicates a malicious document designed to compromise the user's system upon opening.

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://127.0.0.1/applications.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_off00003326.bin rtf-objdata-decoded RTF \objdata at offset 0x3326 2690 bytes
SHA-256: 071cfccee2ff6d908ebd6aa547d10b19c70d6bd714ab1b4edaaa3e5d9d7c34f9