Berbew

Category: infostealer · Aliases: Berbew, Padodor, Trojan:Win32/Berbew, Win32/Berbew, Trojan.Berbew, Backdoor.Padodor, Trojan.Padodor · Sample count (EMBER 2018): 407 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: InfostealerStatus: Automated SignaturePlatform: WINDOWS, X86Stage: Initial-Access, Execution, Persistence, Credential-Access, Collection, Command-And-ControlFirst seen: 2004Actor: Eastern European Cybercrime GroupsIndustry: banking, financial_services, retail, consumersMotivation: Financial Fraud, Certificate Theft & SOCKS Proxy Relaying🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Trojan:Win32/Berbew (widely known in antivirus telemetry as Padodor) is a historic banking trojan and multi-purpose infostealer discovered in 2004 that pioneered early webinject and local proxy interception techniques.

Table of Contents

Overview

Trojan:Win32/Berbew (widely known in antivirus telemetry as Padodor) is a historic banking trojan and multi-purpose infostealer discovered in 2004 that pioneered early webinject and local proxy interception techniques. Operating by injecting its malicious modules into Windows Explorer (explorer.exe) and Internet Explorer, Berbew installs a local proxy engine that monitors HTTP and HTTPS traffic on ports 80 and 443. When users access supported banking institutions, e-commerce platforms, or webmail services, Berbew captures plaintext credentials, steals stored digital certificates, logs keyboard inputs, and exfiltrates financial data to remote servers via hidden web POST requests while simultaneously establishing an open SOCKS proxy backdoor on the infected host.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

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

Known Derivatives & Downstream Variants: Berbew.A (Padodor) · Berbew.B Proxy Build · Berbew Webinject Variant

MITRE ATT&CK Techniques

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

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

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

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-OAAOutbound Network Traffic FilteringIsolateT1090.001Restrict outbound connections to known external proxy relays and enforce enterprise forward proxy authentication.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-PMAPassword Manager Access ControlHardenT1555Enforce device compliance checks and multi-factor biometric authentication before unlocking stored credential vaults.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsHTTP, SOCKS
Observed ports80, 1080
Identifiable from traffic aloneMedium

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.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_BERBEW_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Berbew"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "berbew" ascii wide nocase
        $s2 = "berbew" ascii wide nocase
        $s3 = "padodor" ascii wide nocase
        $s4 = "trojan:win32/berbew" ascii wide nocase
        $s5 = "win32/berbew" ascii wide nocase
        $s6 = "trojan.berbew" ascii wide nocase
        $s7 = "backdoor.padodor" ascii wide nocase
        $s8 = "trojan.padodor" 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 - Berbew (Infostealer) Execution & Triage
id: 04b2a330-e06c-5258-b35b-04ef231a0699
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Berbew 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/berbew
- 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.t1055
- attack.t1555
- attack.t1056_001
- attack.t1090_001
- attack.t1071_001
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_BERBEW_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Berbew 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 = "berbew" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Isolate compromised endpoints to stop unauthorized SOCKS proxy routing and credential leaks.
  2. Terminate injected explorer.exe modules and restore default Windows proxy settings.
  3. Reset credentials for all financial and webmail accounts accessed from the infected workstation.
  4. Apply Microsoft security patch MS04-011 to resolve remote LSASS vulnerability CVE-2004-0115.

What to Avoid

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

  1. Do not allow endpoints to operate with rogue localhost proxy configurations.
  2. Avoid entering financial credentials on systems exhibiting unexpected browser certificate prompts.
  3. Never expose unpatched legacy Windows services to untrusted network segments.

References & External Analysis

Frequently Asked Questions

What is Berbew (Padodor) trojan?

Berbew is an early banking trojan and password stealer that sets up a local proxy to intercept online banking credentials and digital certificates.

How did Berbew intercept web browser traffic?

Berbew modified Windows network settings to establish an internal proxy server, routing browser web traffic through itself to sniff usernames and passwords.

What secondary capabilities did Berbew include?

Berbew included a keylogger, digital certificate stealer, and an open SOCKS proxy server allowing attackers to route fraudulent transactions through the victim's IP.

What vulnerabilities were exploited to spread Berbew?

Berbew exploited network vulnerabilities including Microsoft LSASS buffer overflow CVE-2004-0115 (MS04-011) to compromise unpatched Windows workstations.

How did administrators detect Berbew infections?

Detection involved spotting unauthorized local proxy port configurations, injected modules in explorer.exe, and unauthorized entries in Windows Run registry keys.

How do I remove Berbew from Windows?

Manual removal of Berbew 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 Berbew infection?

Symptoms of Berbew 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 Berbew 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

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