Threat Advisories:
Critical Threat Research : Middle-East at WAR: The Rapidly Escalating Iranian Cyber Threat Download the Report

GoBruteforcer Exposed: How Weak Credentials Power a Silent Linux Botnet

Red | Attack Report
Download PDF

Summary

GoBruteforcer (also known as GoBrut) is a sophisticated and continuously evolving Go-based Linux botnet first discovered in 2023 that has grown significantly more capable through iterative development cycles. This GoBruteforcer malware campaign represents a global threat targeting Linux servers worldwide through systematic brute-force attacks against weak credentials on internet-exposed services including FTP, MySQL, PostgreSQL, and phpMyAdmin administrative interfaces. The GoBruteforcer botnet operates through a meticulously structured multi-stage infection chain incorporating web shells, architecture-specific downloaders, IRC command-and-control bots, and dedicated credential brute-forcing modules.

The widespread success of GoBruteforcer attacks is directly attributable to the proliferation of AI-generated deployment examples and tutorials that propagate common default usernames and insecure credential configurations across countless Linux server deployments. Legacy web application stacks like XAMPP contribute significantly to the GoBruteforcer attack surface by exposing FTP services and administrative interfaces with minimal security hardening, creating easily exploitable entry points. Security researchers estimate that over 50,000 Linux servers remain immediately vulnerable to GoBruteforcer-style credential brute-forcing attacks due to weak authentication configurations on internet-facing services.

The GoBruteforcer operators demonstrate clear financial motivations with specific focus on cryptocurrency infrastructure targeting. Compromised systems are leveraged to deploy specialized Go-based tools designed to scan TRON wallet balances and execute token-sweeping operations against TRON and Binance Smart Chain accounts. Blockchain analysis has confirmed successful cryptocurrency theft operations, with researchers recovering data files containing approximately 23,000 TRON wallet addresses and identifying confirmed fund transfers to attacker-controlled wallets. The 2025 GoBruteforcer variant represents a significant technical evolution, featuring a completely rewritten Go-based IRC bot protected with Garble code obfuscation, advanced process-masking techniques for stealth operations, and more resilient distributed command-and-control infrastructure with multiple fallback mechanisms.

Attack Details

GoBruteforcer Initial Access and Multi-Stage Infection Chain

GoBruteforcer represents a steadily evolving Linux botnet written entirely in the Go programming language that has demonstrated continuous capability expansion since its initial discovery in 2023. Unlike exploit-based malware that relies on software vulnerabilities, GoBruteforcer follows a deliberate multi-stage infection methodology that capitalizes exclusively on weak credential security and exposed network services. The GoBruteforcer initial access phase typically achieves compromise by conducting systematic brute-force attacks against FTP login interfaces, exploiting misconfigured MySQL database servers with weak or default credentials, or breaking into publicly accessible phpMyAdmin administrative panels exposed to the internet without proper access controls.

Systems running XAMPP web application development environments prove particularly attractive targets for GoBruteforcer operations. XAMPP’s default installation configuration frequently exposes FTP services that are directly mapped to web-accessible document root directories, creating a dangerous security condition where successful FTP credential compromise immediately enables attackers to upload and execute malicious code through the web server. This architectural weakness in XAMPP deployments transforms credential-based access into direct code execution capabilities, making these systems priority targets for GoBruteforcer scanning and exploitation activities.

Web Shell Deployment and Command-and-Control Establishment

Once GoBruteforcer attackers successfully compromise initial credentials and gain authenticated access to vulnerable services, they rapidly move to establish persistent control by uploading a PHP-based web shell into the compromised server’s web-accessible document root directory. This GoBruteforcer web shell component functions as a remote command execution console, providing operators with the ability to execute arbitrary system commands on the compromised Linux server and prepare the environment for deployment of additional malware stages. The web shell serves as the critical bridgehead that enables GoBruteforcer’s transition from simple authenticated access to full command execution and persistent compromise.

From the web shell foothold, GoBruteforcer attackers deploy the next critical stage of the infection chain: an IRC-based command-and-control bot. Using the web shell’s command execution capabilities, the operators download and execute architecture-specific compiled binaries matched to the target system’s CPU architecture (x86, x64, or ARM). Once executed, the GoBruteforcer IRC bot establishes outbound connections to attacker-controlled command-and-control infrastructure using the Internet Relay Chat protocol, typically communicating over TCP port 8080 rather than standard IRC ports to evade basic network monitoring.

Distributed Brute-Forcing and Botnet Expansion

The GoBruteforcer IRC bot operates as the central coordination component for all subsequent malicious activities on the compromised host. Through the IRC command-and-control channel, attackers remotely push additional payloads and instructions to the infected system, including a dedicated credential brute-forcing module that is periodically updated with new target lists and credential dictionaries. This GoBruteforcer bruteforcer component operates continuously on compromised systems, systematically scanning random public IP address ranges across the internet and attempting credential-based authentication attacks against any discovered exposed services including FTP, MySQL, PostgreSQL, and other common Linux server applications.

The GoBruteforcer botnet architecture is specifically designed for efficiency and persistence, ensuring that compromised servers function not merely as passive victims but as active participants in expanding the botnet’s reach and harvesting new access credentials across the internet. Each infected system becomes a distributed scanning and brute-forcing node, collectively creating a massive credential-testing infrastructure capable of attempting billions of authentication combinations across millions of potential target systems worldwide.

2025 Technical Evolution and Enhanced Evasion

The 2025 variant of GoBruteforcer represents a substantial technical advancement demonstrating the operators’ ongoing development investment and sophistication. The IRC command-and-control bot component has been completely rewritten in Go programming language and protected with Garble obfuscation technology designed to hinder reverse engineering and malware analysis by security researchers. To maintain operational stealth and avoid detection by system administrators and security monitoring tools, the 2025 GoBruteforcer variant implements advanced process-masking techniques using the Linux prctl system call to manipulate how the malicious process appears in system process listings, frequently disguising itself as the legitimate “init” system process.

The malware additionally overwrites its own command-line arguments in the system process table to further evade detection by tools that examine running process command lines for suspicious patterns. The 2025 GoBruteforcer infrastructure introduces multiple fallback command-and-control mechanisms with redundant IRC servers and alternative communication channels, allowing the botnet to maintain operational continuity even when primary control servers are disrupted or taken down by security organizations. The malware is compiled and distributed in multiple architecture-specific binary builds optimized for x86, x64, and ARM processor architectures to maximize compatibility and reach across the diverse Linux server ecosystem.

Credential Targeting Methodology and Cryptocurrency Focus

At the operational core of GoBruteforcer’s effectiveness lies its systematic and disciplined approach to credential-based exploitation. Each brute-force scanning task executed by infected botnet nodes receives approximately 200 credential combinations from the central command-and-control infrastructure, drawn from larger master dictionaries containing between 375 to 600 commonly reused weak passwords aggregated from data breaches, default configuration documentation, and AI-generated deployment tutorials. The GoBruteforcer credential targeting specifically favors predictable operational usernames frequently found in development environments and tutorials, including “appuser,” “myuser,” “root,” “wordpress,” “admin,” and cryptocurrency-themed username variations that suggest the presence of blockchain-related applications or infrastructure.

The global exposure of vulnerable services creates an enormous attack surface for GoBruteforcer operations. Millions of FTP, MySQL, and PostgreSQL database servers remain publicly accessible from the internet without adequate authentication hardening or network access controls. Security researchers conducting internet-wide scanning estimate that more than 50,000 Linux systems are immediately vulnerable to GoBruteforcer-style brute-force attacks due to weak credential configurations, legacy default passwords, or deployment following insecure AI-generated setup tutorials.

Beyond simple infrastructure compromise and botnet expansion, GoBruteforcer operators demonstrate clear and persistent financial motivations with particular emphasis on cryptocurrency-related targeting. Security researchers analyzing compromised GoBruteforcer-infected hosts have uncovered specialized Go-based tools specifically designed to scan for and exploit cryptocurrency wallet infrastructure. These tools include TRON blockchain balance scanning utilities that query wallet addresses to identify accounts holding valuable cryptocurrency assets, and automated token-sweeping programs capable of draining funds from compromised TRON and Binance Smart Chain wallet accounts by transferring tokens to attacker-controlled addresses.

In documented GoBruteforcer incidents, researchers recovered data files containing approximately 23,000 TRON wallet addresses that had been harvested through botnet operations. Subsequent blockchain forensic analysis confirmed that GoBruteforcer operators successfully executed theft operations, with on-chain transaction records showing confirmed cryptocurrency transfers from victim wallets to addresses controlled by the attackers. This evidence conclusively demonstrates that GoBruteforcer operations extend far beyond theoretical capability or proof-of-concept attacks, representing active and successfully monetized criminal infrastructure conducting real-world cryptocurrency theft at scale.

Recommendations

Comprehensive Internet-Exposed Service Audit

Organizations must immediately conduct comprehensive audits to identify and inventory all FTP, MySQL, PostgreSQL, and phpMyAdmin services that are exposed to internet access on their network perimeters. This GoBruteforcer vulnerability assessment should document which services are accessible from the public internet, what authentication mechanisms protect them, and whether their exposure is operationally necessary. Many GoBruteforcer compromises result from services that were exposed during initial deployment or testing phases and were never properly secured or removed from internet accessibility after their intended use concluded.

Cron Job and Persistence Mechanism Review

Linux system administrators should immediately examine all cron job entries and systemd timer units on production servers for suspicious persistence mechanisms characteristic of GoBruteforcer infections. Particular attention should be focused on scheduled tasks executing binaries from temporary directories including /tmp, /var/tmp, /dev/shm, or /run/lock, as these locations are commonly used by GoBruteforcer malware to store and execute malicious components. Any cron entries referencing unfamiliar binaries, especially those executing with root privileges or connecting to external network resources, should be treated as indicators of potential compromise requiring immediate investigation.

Strong Authentication Enforcement

Organizations must implement and enforce strong password complexity requirements across all FTP, MySQL, PostgreSQL, and phpMyAdmin services to defend against GoBruteforcer credential brute-forcing attacks. Password policies should mandate minimum lengths of 16 characters with mixed case letters, numbers, and special symbols to dramatically increase the computational resources required for successful brute-force attacks. Multi-factor authentication should be deployed for all administrative interfaces wherever technically feasible, adding an additional security layer that GoBruteforcer credential-only attacks cannot bypass. All default and weak credentials for FTP accounts, database users, and administrative interfaces must be immediately rotated to strong unique passwords that do not appear in common password dictionaries or breach databases.

Network Exposure Restriction and Access Control

Security teams should disable or implement strict firewall rules blocking internet-facing FTP, MySQL, and PostgreSQL services unless these exposures are absolutely required for legitimate business operations. For services that must remain accessible, organizations should implement IP address whitelisting that restricts authentication attempts to known trusted source networks, dramatically reducing the attack surface available to GoBruteforcer scanning operations. phpMyAdmin administrative interfaces should never be directly exposed to the internet and should instead be accessible only through VPN connections or from internal management networks, eliminating them as targets for opportunistic GoBruteforcer compromise attempts.

IRC Protocol Traffic Monitoring

Network security monitoring systems should be configured to detect and alert on unusual outbound connections to TCP port 8080 and any IRC protocol activity originating from internal Linux servers. GoBruteforcer command-and-control communications use IRC protocols over non-standard ports to communicate with attacker infrastructure, making these network traffic patterns strong indicators of compromise. Security operations centers should investigate any Linux server initiating outbound IRC connections, as legitimate business applications rarely use this protocol for normal operations.

Indicators of Compromise (IoCs)

Network Infrastructure

IPv4 Addresses: 190[.]14[.]37[.]10, 93[.]113[.]25[.]114

Malicious Domains: fi[.]warmachine[.]su, xyz[.]yuzgebhmwu[.]ru, pool[.]breakfastidentity[.]ru, pandaspandas[.]pm, my.magicpandas[.]fun

Cryptographic Hashes

SHA256: 7423b6424b26c7a32ae2388bc23bef386c30e9a6acad2b63966188cb49c283ad, 8fd41cb9d73cb68da89b67e9c28228886b8a4a5858c12d5bb1bffb3c4addca7c, bd219811c81247ae0b6372662da28eab6135ece34716064facd501c45a3f4c0d, b0c6fe570647fdedd72c920bb40621fdb0c55ed217955557ea7c27544186aeec, ab468da7e50e6e73b04b738f636da150d75007f140e468bf75bc95e8592468e5, 4fbea12c44f56d5733494455a0426b25db9f8813992948c5fbb28f38c6367446, 64e02ffb89ae0083f4414ef8a72e6367bf813701b95e3d316e3dfbdb415562c4, c7886535973fd9911f8979355eae5f5abef29a89039c179842385cc574dfa166

MITRE ATT&CK TTPs

Initial Access (TA0001)

T1110 – Brute Force: GoBruteforcer achieves initial access through systematic brute-force attacks against authentication interfaces on internet-exposed services.

T1110.001 – Password Guessing: The botnet employs password guessing attacks using dictionaries of 375-600 common weak passwords to compromise FTP, MySQL, PostgreSQL, and phpMyAdmin services.

T1190 – Exploit Public-Facing Application: GoBruteforcer targets publicly accessible services and administrative interfaces exposed to the internet without adequate access controls.

Execution (TA0002)

T1059 – Command and Scripting Interpreter: GoBruteforcer executes malicious commands and scripts on compromised Linux systems through multiple interpreter mechanisms.

T1059.004 – Unix Shell: The malware executes shell commands on compromised Linux hosts through web shells and direct command execution capabilities.

T1059.006 – Python: Some GoBruteforcer components utilize Python scripts for specific operational tasks and auxiliary functionality.

Persistence (TA0003)

T1053 – Scheduled Task/Job: GoBruteforcer establishes persistence mechanisms to survive system reboots and maintain long-term access.

T1053.003 – Cron: The malware creates cron job entries on Linux systems to ensure automatic execution of malicious binaries at system startup or scheduled intervals.

T1505 – Server Software Component: GoBruteforcer compromises server software components to maintain persistent access.

T1505.003 – Web Shell: PHP-based web shells are deployed to compromised web servers, providing persistent command execution capabilities independent of other malware components.

Defense Evasion (TA0005)

T1027 – Obfuscated Files or Information: GoBruteforcer employs code obfuscation techniques to hinder malware analysis and evade detection.

T1027.002 – Software Packing: The 2025 variant uses Garble obfuscation to protect Go-based binaries from reverse engineering.

T1070 – Indicator Removal: GoBruteforcer implements techniques to remove or obscure indicators of compromise that might reveal its presence.

T1036 – Masquerading: The malware disguises its processes to appear as legitimate system services, frequently masquerading as the “init” process using prctl system calls.

Credential Access (TA0006)

T1110 – Brute Force: The dedicated bruteforcer module continuously attempts authentication attacks across the internet to harvest credentials from vulnerable systems.

T1110.001 – Password Guessing: GoBruteforcer systematically tests known weak passwords and common default credentials against discovered services.

Discovery (TA0007)

T1082 – System Information Discovery: The malware collects system information from compromised hosts to determine architecture, installed services, and operational capabilities.

T1083 – File and Directory Discovery: GoBruteforcer reconnaissance identifies files, directories, and configurations of interest on compromised systems.

T1046 – Network Service Discovery: The botnet continuously scans random internet IP ranges to discover exposed services vulnerable to credential brute-forcing.

Collection (TA0009)

T1005 – Data from Local System: GoBruteforcer collects cryptocurrency wallet data, configuration files, and other valuable information from compromised Linux systems.

Command and Control (TA0011)

T1071 – Application Layer Protocol: The botnet uses standard application layer protocols for command-and-control communications.

T1071.001 – Web Protocols: Initial compromise and web shell communications occur over HTTP/HTTPS protocols.

T1095 – Non-Application Layer Protocol: GoBruteforcer employs IRC protocol for command-and-control communications, typically over TCP port 8080.

Exfiltration (TA0010)

T1041 – Exfiltration Over C2 Channel: Stolen cryptocurrency wallet data and harvested credentials are exfiltrated through established command-and-control channels.

Impact (TA0040)

T1496 – Resource Hijacking: Compromised systems are leveraged for distributed brute-forcing operations, hijacking computational resources for botnet expansion.

T1657 – Financial Theft: GoBruteforcer operators conduct direct cryptocurrency theft through wallet scanning and token-sweeping operations targeting TRON and Binance Smart Chain accounts.

References

https://research.checkpoint.com/2026/inside-gobruteforcer-ai-generated-server-defaults-weak-passwords-and-crypto-focused-campaigns/

What’s new on HivePro

Get through updates and upcoming events, and more directly in your inbox