Zwangi

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Browser Extension Forcing: It installs malicious extensions or add-ons across all major web browsers. It specifically abuses Windows Group Policy Object (GPO) modifications to "force-install" these extensions, graying out the "Remove" button in the browser settings so the user cannot disable them.
• Search Hijacking and Redirection: The adware alters the browser's default search engine and homepage. Legitimate search queries are intercepted and routed through attacker-controlled domains to artificially inflate traffic metrics for affiliate programs.
• Registry and Service Persistence: Zwangi installs background Windows Services and multiple registry `Run` keys that constantly monitor the system. If a user manages to delete the browser extension, the background service will immediately reinstall it.

Threat Assessment

Incident Response and Remediation

• Remediation of Group Policies: Standard AV will fail to remove Zwangi if the GPOs are not cleared first. IT staff must inspect the local Group Policy settings (e.g., `Computer Configuration\Administrative Templates\Google\Google Chrome\Extensions`) to remove the forced extension IDs.
• Safe Mode Antivirus Scan: Boot the machine into Windows "Safe Mode" to prevent Zwangi's persistent background services from loading. Then, utilize an enterprise-grade anti-malware solution capable of removing deeply embedded PUPs.
• Browser Factory Reset: After the GPOs and registry keys are cleared, perform a complete factory reset of all installed web browsers to clear the hijacked search settings and tracking cookies.

Known aliases

Threat reports may refer to this family under multiple names:

• Adware.Zwangi
• PUP.Zwangi
• BrowserHijacker.Zwangi
• Win32/Zwangi

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:

• T1185: Enforce strong MFA and use browser isolation or hardened browsers for sensitive financial or administrative portals to defeat session hijacking.

MITRE D3FEND™ Defensive Countermeasures

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

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_ZWANGI_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Zwangi"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "zwangi" ascii wide nocase
        $s2 = "adware.zwangi" ascii wide nocase
        $s3 = "pup.zwangi" ascii wide nocase
        $s4 = "browserhijacker.zwangi" ascii wide nocase
        $s5 = "win32/zwangi" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Zwangi (Ransomware) Execution & Triage
id: 0d0a7355-b90d-5b02-8548-6da184dc6173
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Zwangi malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/zwangi
- 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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1562_001
- attack.t1185
- attack.t1112
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_ZWANGI_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Zwangi 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 = "zwangi" 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. Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Zwangi from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Zwangi symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Zwangi to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Zwangi binary and related persistence hooks are eradicated.

What to Avoid

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

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Zwangi.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Zwangi eradication is completely verified.

References & External Analysis

• Search "zwangi" on VirusTotal (External Analysis)
• Search "zwangi" on Any.Run (Sandbox Sandbox)
• Search "zwangi" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Konus
• Zs0Bbeypkrh
• Lyposit
• Killnotes
• Suviapen
• Flowspirit
• Firstinj
• Miancha

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/zwangi.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.