Buzus

Category: trojan · Aliases: Trojan:Win32/Buzus, Trojan.Win32.Buzus, Trojan.Buzus, Trojan:Win32/Buzus.C · Sample count (EMBER 2018): 69 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2008Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Credential Theft & Espionage🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 8.1
Executive Summary
Buzus (cataloged in antivirus vendor databases and threat intelligence taxonomies under detections including Trojan:Win32/Buzus, Trojan.Win32.Buzus, and Trojan.Buzus) is an extensive and enduring family of Windows trojans, spyware, and initial access backdoors active since 2008.

Table of Contents

Overview

Buzus (cataloged in antivirus vendor databases and threat intelligence taxonomies under detections including Trojan:Win32/Buzus, Trojan.Win32.Buzus, and Trojan.Buzus) is an extensive and enduring family of Windows trojans, spyware, and initial access backdoors active since 2008. Widely tracked by Kaspersky and Microsoft across hundreds of granular sub-variants, Buzus frequently functions as the payload component dropped by mass-propagating worms (such as Rimecud) and malicious spam attachments. Once installed, Buzus injects code into system processes like svchost.exe, establishes autostart persistence via Windows registry Run keys, and monitors victim activity. It captures keystrokes, steals credentials stored in web browsers and email clients, and logs active application windows. Furthermore, Buzus maintains encrypted command-and-control channels to download secondary malware strains, turning infected endpoints into multipurpose bots.

Known aliases

Threat reports may refer to this family under multiple names:

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: Classic Win32 Spyware & Backdoor Architectures

Known Derivatives & Downstream Variants: Buzus.C · Buzus.Bipi · Buzus.Bkie

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-NDFNetwork Data FilteringIsolateT1048Inspect non-standard port traffic and block unauthorized ICMP or DNS tunneling protocols at the network perimeter.
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-CVHCredential Vault HardeningHardenT1555.003Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers.
D3-PMAPassword Manager Access ControlHardenT1555.004Enforce device compliance checks and multi-factor biometric authentication before unlocking stored credential vaults.

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_BUZUS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Buzus"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "buzus" ascii wide nocase
        $s2 = "trojan:win32/buzus" ascii wide nocase
        $s3 = "trojan.win32.buzus" ascii wide nocase
        $s4 = "trojan.buzus" ascii wide nocase
        $s5 = "trojan:win32/buzus.c" 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 - Buzus (Trojan) Execution & Triage
id: 24e7972b-68e2-59f5-aa69-29738efce783
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Buzus 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/buzus
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1055
- attack.t1555_003
- attack.t1547_001
- 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

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_BUZUS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Buzus 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 = "buzus" 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. 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

Frequently Asked Questions

What is Trojan:Win32/Buzus?

Buzus is a widespread family of Windows trojans and spyware that steals credentials and logs user activity.

How does Buzus monitor infected endpoints?

It hooks keyboard inputs, logs active application windows, captures screenshots, and extracts saved browser passwords.

Which malware families frequently drop Buzus?

It is frequently dropped by mass-spreading worms such as Rimecud and through weaponized email attachments.

How does Buzus evade detection on Windows?

It injects code into trusted system processes like svchost.exe and decrypts its strings only during runtime.

What remediation is recommended for Buzus infections?

Quarantine the infected binary, inspect the registry for autostart entries, and change passwords on a secure machine.

How do I remove Buzus from Windows?

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

Symptoms of Buzus 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 Trojans

Want to prevent Buzus and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 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 Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/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, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.