Security & Infrastructure Tools
Russian hackers turn Kazuar backdoor into modular P2P botnet
Russian hacker group Secret Blizzard has upgraded the Kazuar backdoor into a modular, peer-to-peer botnet designed for long-term persistence, stealth, and data exfiltration. The malware now uses three modules—Kernel (leader election and task orchestration), Bridge (external C2 proxy), and Worker (keylogging, screenshots, data harvesting, and reconnaissance)—with around 150 configurable options, including AMSI, ETW, and WLDP bypasses. Communications are AES-encrypted and protobuf-serialized via IPC. Microsoft warns this evolution increases evasion, urging defenses to emphasize behavioral detection. The botnet targets government and critical infrastructure across Europe, Asia, and Ukraine.

RUSSIAN HACKERS TURN KAZUAR BACKDOOR INTO MODULAR P2P BOTNET
Overview
- A well-known backdoor nicknamed Kazuar has been reimagined by the Russian hacker group Secret Blizzard as a modular peer-to-peer botnet. The redesigned toolkit emphasizes long-term persistence, stealthy operation, and expanded data-collection capabilities.
- Secret Blizzard’s activity intersects with other prominent groups such as Turla, Uroburos, and Venomous Bear, and the group has associations with the Russian intelligence sphere. Its targets span government and diplomatic sectors, defense-related entities, and critical infrastructure across Europe, Asia, and Ukraine.
- Kazuar’s lineage stretches back to the mid-2000s, with public documentation of the malware tracing to 2017 and attribution to Turla over time. Its evolution into a modular P2P framework represents a shift toward autonomous operation and resilient command-and-control (C2) structures.
Background and Evolution
- The Kazuar backdoor first appeared in security histories years ago, evolving through multiple iterations as operators refined its capabilities and deployment methods.
- Earlier campaigns included attacks against European government organizations, with later activity expanding to Ukraine among other targets. The latest iteration redefines Kazuar as a self-contained, modular botnet designed for persistent access and covert data gathering.
- The new variant introduces a three-module architecture that enables distributed control, covert communications, and specialized espionage functions. This architecture is intended to complicate attribution and raise the bar for defender detection.
Modular Architecture: Kernel, Bridge, and Worker
- Kernel module: Serves as the central coordinator and task manager. It oversees other modules, elects a leader, and orchestrates data flow and communications across the botnet. In practice, the leader is one infected host that interfaces with the C2 server, receives tasks, and disseminates instructions regionally to other infected machines. Non-leader hosts operate in a low-visibility, “silent” mode to reduce detection risk.
- Leader selection: The system autonomously determines the Kernel leader based on uptime, reboot history, and disruption counts. This internal election process helps the botnet maintain resilient coordination even under active defense.
- Bridge module: Acts as an external communications proxy, relaying traffic between the elected Kernel leader and the remote C2 infrastructure. It supports multiple transport channels, including HTTP, WebSocket streams, and Exchange Web Services (EWS) to blend with legitimate network traffic.
- Worker module: Carries out the actual espionage work. Typical capabilities include keylogging, screen capture, file system harvesting, reconnaissance of systems and networks, collection of email/MAPI data (notably Outlook data), window monitoring, and retrieval of recently used files.
Internal Communications and Data Handling
- Inter-process communication (IPC) inside infected hosts relies on Windows messaging, Mailslots, and named pipes. These channels are designed to mimic normal operational noise while enabling coordinated actions across the botnet.
- Communications are encrypted with AES and serialized using Google Protocol Buffers (Protobuf), providing a compact and tamper-resistant data flow between components.
- The data collection and exfiltration pipeline follows a staged approach: the Worker gathers data locally, stores it securely, and then transmits it to the Bridge, which coordinates exfiltration toward the C2.
Types of System Information Collected
- Kazuar is described as gathering a broad set of system information that can inform targeting and exfiltration decisions. This includes details about the operating system, host identifiers, hardware configuration, installed software, and running processes. The captured data is then prepared for staged exfiltration through the Bridge.
Configurability and Security Bypasses
- The new Kazuar variant supports a large configuration surface—about 150 options that operators can enable or disable. These options govern security bypass capabilities, task scheduling, timing and size of data theft, process injection, task management, and command execution, among other behaviors.
- Notable security bypasses mentioned include:
- Antimalware Scan Interface (AMSI) bypass
- Event Tracing for Windows (ETW) bypass
- Windows Lockdown Policy (WLDP) bypass
- This high degree of configurability makes the threat adaptable to different environments and difficult to pin down with static signatures alone.
Threat Actor Profile and Persistence Goals
- Secret Blizzard operates with a long-term persistence objective in mind, aiming to maintain access for intelligence collection over extended periods.
- The exfiltration focus includes documents and email content that may have political significance, underscoring a strategic emphasis on information that can influence decision-making or diplomatic positions.
- The activity footprint emphasizes stealth, limited direct contact with the C2, and distributed control designed to sustain operations even under partial containment.
Security Implications and Industry Context
- Analysts observing the variant highlight its modular design, stealthy operation, and extensive configurability as factors that complicate detection and response.
- The architecture minimizes obvious external chatter by distributing leadership and routing communications through proxy components, while still maintaining robust data collection and control capabilities.
- In discussions around defenses, emphasis is placed on understanding behavioral patterns and the orchestration of tasks across modules rather than relying solely on static signatures. This reflects a broader trend in defending against sophisticated, state-aligned threat actors.
Conclusion
- The Kazuar backdoor has evolved from a traditional espionage tool into a modular P2P botnet designed for resilience, stealth, and targeted data collection.
- By separating responsibilities into kernel, bridge, and worker components and enabling autonomous leader selection, the threat achieves a balance between centralized coordination and distributed covert operations.
- The combination of advanced bypass techniques, encrypted internal communications, and extensive configurability positions Kazuar as a challenging adversary for defenders monitoring government, defense, and critical infrastructure networks.


