Bypass
Table of Contents
Overview
Bypass (classified in antivirus detection telemetry under designations including PWS:Win32/Bypass, PWS.Win32.Bypass, and Win32/Bypass) is a dedicated information theft malware engineered to harvest stored credentials, browser session cookies, cryptocurrency wallets, and keystrokes. Disseminated across enterprise networks and consumer workstations via social engineering, phishing attachments, malicious drive-by downloads, or weaponized software cracks, Bypass executes an initial reconnaissance phase upon system ingress. The binary evaluates host privileges, detects active hypervisors and sandbox environments to evade behavioral analysis, and establishes resilient autostart persistence by configuring registry keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run or registering background Windows services. Operational mechanics characteristic of this family include credential database extraction, API hooking, system discovery, and encrypted C2 exfiltration. Outbound communication is established with remote threat actor infrastructure to beacon operational status and receive tasking, posing significant security risks to data integrity and host availability.
Known aliases
Threat reports may refer to this family under multiple names:
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1548.002 | Abuse Elevation Control Mechanism: Bypass User Account Control | Privilege Escalation | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
T1055 | Process Injection | Defense Evasion | ATT&CK ↗ |
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-PIAD | Process Injection Analysis & Detection | Detect | T1055 | Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC). |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_BYPASS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Bypass"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "bypass" ascii wide nocase
$s2 = "hacktool.bypass" ascii wide nocase
$s3 = "exploit.uacbypass" ascii wide nocase
$s4 = "tool.evasion" ascii wide nocase
$s5 = "riskware.bypass" ascii wide nocase
$s6 = "pws:win32/bypass" ascii wide nocase
$s7 = "pws.win32.bypass" ascii wide nocase
$s8 = "win32/bypass" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Bypass (Infostealer) Execution & Triage
id: ce5c2e04-01e6-580c-b140-881ca7db4433
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Bypass malware family. Detects browser credential database harvesting,
master key queries, and DPAPI extraction routines typical of modern infostealers.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/bypass
- https://malware-families-catalog.systemhelpdesk.com/defensive/infostealer-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.infostealer
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1555
- attack.t1056_001
- attack.t1114
- attack.t1041
- attack.t1082
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \rundll32.exe
CommandLine|contains:
- \Google\Chrome\User Data\Default\Login Data
- \AppData\Roaming\Mozilla\Firefox\Profiles
- \AppData\Local\Microsoft\Edge\User Data
- vaultcmd.exe /list
- dpapi
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_BYPASS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Bypass 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 = "bypass" 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.
- Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Bypass from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
- Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Bypass symmetric encryption keys or uncompiled payload components may still reside in memory.
- 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 Bypass to inhibit recovery.
- 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.
- Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Bypass 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.
- Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Bypass.
- Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
- Do not connect clean backup drives or external storage to the affected network until Bypass eradication is completely verified.
References & External Analysis
Frequently Asked Questions
What is PWS:Win32/Bypass?
Bypass is a infostealer threat designed to infiltrate Windows systems and execute unauthorized operations without user consent.
How does Bypass compromise target systems?
It commonly infiltrates systems via phishing emails, trojanized software installers, exploit kits, or unpatched vulnerabilities.
What persistence mechanisms does Bypass utilize?
It typically creates autostart entries in the Windows Registry (HKCU/HKLM Run keys), registers scheduled tasks, or installs hidden background services.
What risks does Bypass pose to an enterprise?
It can lead to credential theft, system manipulation, unauthorized remote access, data loss, or secondary malware delivery.
How can administrators detect and eliminate Bypass?
Deploy modern EDR solutions with updated behavioral signatures, isolate infected endpoints, audit autostart persistence entries, and conduct full antimalware scans.
How do I remove Bypass from Windows?
Manual removal of Bypass is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
What are the main symptoms of a Bypass infection?
Symptoms of Bypass can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Infostealers
Want to prevent Bypass and similar threats from compromising your organization? Read our comprehensive defensive guide: InfoStealer Protection & Remediation.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/bypass.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.