Malicious RTF — malware analysis report

Static analysis result for SHA-256 02d1c90c226026e2…

MALICIOUS

RTF

109.8 KB First seen: 2017-12-24
MD5: d383d43d4cdb4c4972c2541f3412832d SHA-1: 2342d60396e7ee232cd78e9c3145eb1930daf3c5 SHA-256: 02d1c90c226026e2ec97b30d450a7620c59e212e6ab16638984ac42bb86cc73e
222 Risk Score

Malware Insights

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

The RTF file contains OLE object data that leverages CVE-2017-0199 or CVE-2017-8759 to automatically activate a remote loader. The embedded URL, http://new.wex-online.co/d/u.php?stats=send&thread=0, is used to fetch and execute a secondary payload. ClamAV also detected this as a downloader variant.

Heuristics 6

  • CVE-2017-0199 / CVE-2017-8759 (OLE2Link auto-activated remote loader) critical CVE related RTF_OLE2LINK_REMOTE_MONIKER_LOADER
    RTF embeds an OLE2Link object that is force-activated with \objupdate (no user interaction on open) and fetches a remote second stage — through an INCLUDETEXT/INCLUDEPICTURE field or the OLE object's own moniker. This is the OLE2Link auto-update attack path shared by CVE-2017-0199 (server returns an HTA/scriptlet) and CVE-2017-8759 (server returns a SOAP WSDL the .NET parser compiles). Office processes the fetched response through the same code path; the specific CVE depends on the now-unreachable server content type.
  • ClamAV: Rtf.Downloader.CVE_2017-6336326-3 critical CLAMAV_DETECTION
    ClamAV detected this file as malware: Rtf.Downloader.CVE_2017-6336326-3
  • \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.
  • INCLUDETEXT/INCLUDEPICTURE remote URL high RTF_INCLUDE_REMOTE
    RTF document uses INCLUDETEXT or INCLUDEPICTURE with an http:// URL — Word can fetch the remote content on open depending on Office version and external-content settings, enabling remote template injection, NTLM capture via redirects, or payload delivery
  • OLE object data medium RTF_OBJDATA
    RTF contains 2 \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://new.wex-online.co/d/u.php?stats=send&thread=0 In RTF body

Extracted artifacts 2

Files carved from inside the sample during analysis.

FilenameKindSourceSize
objdata_00_off000188ef.bin rtf-objdata-decoded RTF \objdata at offset 0x188EF 2706 bytes
SHA-256: ab12e55b5a00d856d928562188e130f5a2f47375f0e8768e2e33d670f7f5445f
objdata_01_off0001a01d.bin rtf-objdata-decoded RTF \objdata at offset 0x1A01D 2830 bytes
SHA-256: 1b820f9a56e85e1287acfb5435c498ac9987cd4b0e94b1e0607a9ba754a28747

Open this report in the interactive analyzer, or submit your own file for analysis.