Buzus

Category: trojan_generic · Aliases: None known · Sample count (EMBER 2018): 69 · Enrichment: expert-seo · Updated: 2026-06-09

Overview

Trojan:Win32/Buzus is a persistent, targeted trojan designed specifically to infiltrate endpoints and aggressively harvest sensitive credentials, including saved browser passwords, FTP logins, and cryptocurrency wallet data.

Understanding Buzus
To the end-user, a Buzus infection is entirely invisible. There are no pop-ups, no ransom notes, and no obvious system sluggishness. For threat intelligence analysts, Buzus represents an 'Infostealer'. Its sole purpose is to quietly gather as much valuable authentication data as possible, compress it into a hidden archive, and exfiltrate it to the attacker's Command-and-Control (C2) server.

Execution and Evasion Strategies
Buzus is typically distributed via spearphishing campaigns containing weaponized Office documents (macro-enabled) or as a secondary payload dropped by other malware. Upon execution, it utilizes packing and obfuscation to evade static AV signatures. It rapidly iterates through standard credential storage locations: parsing browser SQLite databases (Chrome `Login Data`, Firefox `logins.json`), querying the Windows Credential Manager, and searching for specific files associated with FTP clients (FileZilla) and cryptocurrency wallets. Buzus establishes persistence, often via Registry Run keys, to ensure it captures any newly entered credentials. It frequently injects its credential-harvesting routines into legitimate processes to mask its activities.

Indicators of Compromise & Impact
The impact is a massive loss of credential security, often leading to subsequent data breaches or financial theft. Threat hunters should investigate EDR alerts for 'Suspicious File Read' activity targeting browser databases. Network logs will reveal Buzus reaching out to C2 domains using encrypted traffic, often transmitting data via POST requests or SMTP. The presence of newly created, hidden ZIP or RAR archives in the `%Temp%` directory is a strong indicator of staged data pending exfiltration.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

TechniqueNameTactic
T1555.003Credentials from Password Stores: Credentials from Web BrowsersCredential Access
T1555.004Credentials from Password Stores: Windows Credential ManagerCredential Access
T1056.001Input Capture: KeyloggingCollection
T1048Exfiltration Over Alternative ProtocolExfiltration
T1055Process InjectionDefense Evasion

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_BUZUS {
    meta:
        description = "Detects Buzus (trojan_generic)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "buzus" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Buzus Activity
id: c3d8914f242bbaa50bd1581406ef606c
status: experimental
description: Detects generic indicators of the buzus malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*buzus*"
    condition: selection
level: medium

Containment & Response Steps

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

  1. Instantly isolate the endpoint from the network to halt the active exfiltration of the harvested credential archives.
  2. Force a global, mandatory password reset for the compromised user, prioritizing corporate VPN access, email accounts, and financial portals.
  3. Capture a full forensic memory image to extract the active Buzus payload and identify the specific C2 infrastructure it is communicating with.
  4. Assume all locally saved passwords have been compromised; perform a clean OS rebuild to ensure the infostealer is completely eradicated.

What to Avoid

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

  1. Do not allow the user to type any passwords or access sensitive portals while the machine is infected, as the infostealer may include keylogging capabilities.
  2. Avoid assuming the threat is contained just by removing the executable; the exfiltrated passwords must be reset globally.

References & External Analysis

Related Families (Category: trojan_generic)

Explore other malware families in the same category:

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

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/buzus.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, Replit, StackBlitz, CodeSandbox, and CodePen.