Wews

Overview

Wews (recognized across threat telemetry signatures as Exploit:HTML/Wews, Exploit.HTML.Wews, and Trojan-Downloader.HTML.Wews) is a specialized class of malicious web-based exploit scripts active since 2013. Designed to weaponize browser rendering engines, Wews payloads are delivered via drive-by download compromise portals, malvertising networks, and prominent exploit kit frameworks (including Angler, Sweet Orange, and Fiesta). When a victim navigates to a compromised webpage hosting Wews, heavily obfuscated JavaScript executes in the background to fingerprint the client browser, operating system architecture, and installed plugin versions (such as Adobe Flash, Oracle Java, or Internet Explorer modules). Upon detecting a vulnerable rendering component, the script triggers heap spraying and memory corruption exploits to escape browser sandboxes and execute arbitrary shellcode. Once initial code execution is established, Wews silently fetches and runs secondary binaries—such as banking trojans, information stealers, or ransomware droppers—directly in system memory without requiring user interaction.

Known aliases

Threat reports may refer to this family under multiple names:

• Exploit:HTML/Wews
• Exploit.HTML.Wews
• Trojan-Downloader.HTML.Wews
• HTML/Wews

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Drive-By Download Exploit Kits

Known Derivatives & Downstream Variants: Exploit:Html/Wews.A · Exploit:Html/Wews.B

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1059.007: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

• 1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c
• 2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d

Delivery vectors

• Compromised website iframes and malvertising networks
• Exploit kit landing page redirects

Persistence mechanisms

• Secondary dropped payload execution via Windows Scheduled Tasks
• HKCU\Software\Microsoft\Windows\CurrentVersion\Run

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_WEWS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Wews"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "wews" ascii wide nocase
        $s2 = "exploit:html/wews" ascii wide nocase
        $s3 = "exploit.html.wews" ascii wide nocase
        $s4 = "trojan-downloader.html.wews" ascii wide nocase
        $s5 = "html/wews" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Wews (Exploit) Execution & Triage
id: ef563247-dc08-5fe9-8b32-a034eed44714
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Wews malware family. Detects suspicious execution from temporary user directories
  with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/wews
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.exploit
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1189
- attack.t1203
- attack.t1059_007
- attack.t1027
- attack.t1105
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_WEWS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Wews tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "wews" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. Review endpoint EDR telemetry to verify whether the browser process spawned suspicious child processes (e.g., cmd.exe, powershell.exe).
2. If an anomalous child process or secondary dropped executable is detected, isolate the machine immediately.
3. Block the malicious domain and exploit landing URLs at the enterprise proxy and web application gateway.
4. Ensure browser updates and security patches are enforced across all workstations to remediate underlying rendering vulnerabilities.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not assume the machine is clean merely because antivirus blocked the HTML file, as the shellcode may have already executed in memory.
2. Avoid permitting unvetted browser plugins or legacy script rendering engines to run in enterprise environments.

References & External Analysis

• Microsoft Defender Threat Encyclopedia - Exploit:HTML/Wews
• Trend Micro Security Intelligence - Exploit-HTML
• Search "wews" on VirusTotal (External Analysis)
• Search "wews" on Any.Run (Sandbox Sandbox)
• Search "wews" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/wews.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.