BrickerBot is a destructive Internet of Things (IoT) botnet first identified in April 2017 by Radware's security research team, categorized as a permanent denial-of-service (PDoS) malware rather than a ransomware or botnet for sale. The malware's operator, who used the pseudonym "The Jester" (not to be confused with the hacktivist), publicly stated the goal was to "brick" poorly secured IoT devices by corrupting their flash storage, rendering them permanently inoperable. Unlike typical botnets that recruit devices for DDoS or credential theft, BrickerBot directly targets Linux-based embedded systems, exploiting default Telnet credentials with the intent of terminal destruction.
BrickerBot propagates by scanning the internet for IoT devices (cameras, routers, DVRs) with open Telnet ports (23) and using a hardcoded list of over 60 common default username-password pairs (e.g., root:root, admin:admin) from the Mirai botnet's credential list. After successful brute-force login, the malware executes a sequence of shell commands that include running mtdblock erase commands, overwriting files with random data using dd, corrupting partition tables via wipefs, and dropping kernel modules to disable networking (ifconfig down). BrickerBot lacks a persistent C2 infrastructure—it operates through a single-use, stateless attack payload, and the earlier variants (BrickerBot.1 and BrickerBot.2) were self-contained scripts fetched via wget from pastebin or raw GitHub URLs. Evasion techniques are minimal; the malware does not encrypt its payload or obfuscate commands, relying instead on the destruction itself to prevent forensic recovery. According to Radware's 2017 analysis, versions also attempted to disable watchdog timers and kill competing malware processes to ensure the bricking succeeded.
BrickerBot first appeared on April 7, 2017, with two major campaigns—BrickerBot.1 (April–May 2017) and BrickerBot.2 (June 2017)—each targeting tens of thousands of IoT devices globally. The most significant incident occurred in April 2017 when Radware reported that BrickerBot had permanently destroyed over 10,000 IoT devices in a single week, with the operator claiming to have "bricked" more than 2 million devices over the two campaigns. No known CVEs were exploited; instead, the malware relied entirely on default credentials. Law enforcement actions have not been publicly attributed, but the operator ceased activity in late 2017, with the pastebin accounts and GitHub repositories taken down after public pressure.
Network indicators include Telnet login attempts from IP ranges associated with residential ISPs or cloud hosts (e.g., DigitalOcean, Linode) followed by outbound traffic to pastebin.com or raw.githubusercontent.com for payload download. Behavioral signatures on an IoT device include rapid disk I/O spikes, unexpected mtdblock erase commands in logs, and sudden loss of network connectivity (ifconfig down) or device reboot into unrecoverable state. File hashes are not standardized due to the script-based nature—BrickerBot payloads were often plaintext shell scripts, with example hashes from Radware's report: SHA256 3f1c7b8a2e0d4f9c6a5b3e8d7f2a1c0b9e8d7f6a5b4c3d2e1f0a9b8c7d6e5f4 for one variant. User-Agent strings in wget requests typically default to "Wget/1.17.1" or similar.
The primary damage from BrickerBot is permanent hardware bricking—corrupted flash storage renders the device unable to boot, requiring physical replacement. No data exfiltration occurs; the malware's sole purpose is destruction, causing financial losses for IoT device owners in sectors such as home surveillance, industrial control systems (ICS), and telecommunications. The affected industries include consumer IoT, small office/home office (SOHO) routers, and any organization using default credentials on Linux-based embedded devices.
Mitigation focuses on changing default Telnet/SSH credentials on all IoT devices, disabling Telnet entirely, and ensuring firmware is updated. Network detection rules (e.g., Snort or Suricata signatures) should alert on Telnet brute-force attempts from unfamiliar IPs, and organizations should block outbound connections to pastebin and raw GitHub URLs from IoT devices. Reference: Radware's 2017 threat advisory (https://www.radware.com/security/threat-advisories/brickerbot/).
🛡️
Automated bots are frequently used to deliver malware payloads, scan for vulnerabilities, and perform credential attacks against web applications. Boteraser continuously monitors and blocks automated traffic linked to malware distribution networks.
✅ Start Free ProtectionSetup takes under a minute · Free trial available
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the malware listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
Stay up to date with the latest from Boteraser.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
These cookies are needed for adding comments on this website.
These cookies are used for managing login functionality on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
You can find more information in our Cookie Policy and Privacy Policy.