BrickerBot
{{short description|Destructive malware targeting IoT devices}}
{{use mdy dates |date=December 2020}}
BrickerBot was malware that attempted to permanently destroy ("brick") insecure Internet of Things devices. BrickerBot logged into poorly-secured devices and ran harmful commands to disable them. It was first discovered by Radware after it attacked their honeypot in April 2017. On December 10, 2017, BrickerBot was retired.
The most infected devices were in Argentina, followed by North America and Europe, and Asia (including India).{{cite web |title=BrickerBot: "The Doctor's" PDoS Attack Has Killed Over 2 Million Insecure Devices |url=https://fossbytes.com/brickerbot-malware-pdos-attack-iot-device/ |website=Fossbytes |date=25 April 2017}}
Discovery
= BrickerBot.1 and BrickerBot.2 =
The BrickerBot family of malware was first discovered by Radware on April 20, 2017, when BrickerBot attacked their honeypot 1,895 times over four days. BrickerBot's method of attack was to brute-force the telnet password, then run commands using BusyBox to corrupt MMC and MTD storage, delete all files, and disconnect the device from the Internet. Less than an hour after the initial attack, bots began sending a slightly different set of malicious commands, indicating a new version, BrickerBot.2. BrickerBot.2 used the Tor network to hide its location, did not rely on the presence of busybox on the target, and was able to corrupt more types of storage devices.{{cite web|title="BrickerBot" Results In PDoS Attack|url=https://security.radware.com/ddos-threats-attacks/brickerbot-pdos-permanent-denial-of-service/|website=Radware|access-date=February 26, 2018|date=April 5, 2017}}
= BrickerBot.3 and BrickerBot.4 =
BrickerBot.3 was detected on May 20, 2017, one month after the initial discovery of BrickerBot.1. On the same day, one device was identified as a BrickerBot.4 bot. No other instances of BrickerBot.4 were seen since.{{cite web|title=BrickerBot PDoS Attack: Back With A Vengeance|url=https://security.radware.com/ddos-threats-attacks/brickerbot-pdos-back-with-vengeance/|website=Radware|access-date=February 26, 2018|date=April 21, 2017}}
Shutdown and Impact
According to Janit0r, the author of BrickerBot, it destroyed more than ten million devices before Janit0r announced the retirement of BrickerBot on December 10, 2017.{{cite web |last1=Shattuck |first1=Justin |title=BrickerBot: Do "Good Intentions" Justify the Means—or Deliver Meaningful Results? |url=https://www.f5.com/labs/articles/threat-intelligence/brickerbot-do-good-intentions-justify-the-meansor-deliver-meaningful-results |website=F5 Labs |access-date=January 21, 2019|language=en |date=December 28, 2017}} In an interview with Bleeping Computer, Janit0r stated that BrickerBot was intended to prevent devices from being infected by Mirai.{{cite web |last1=Cimpanu |first1=Catalin |title=BrickerBot Author Retires Claiming to Have Bricked over 10 Million IoT Devices |url=https://www.bleepingcomputer.com/news/security/brickerbot-author-retires-claiming-to-have-bricked-over-10-million-iot-devices/ |website=BleepingComputer |access-date=4 August 2018 |language=en-us |date=11 December 2017}}{{cite web |last1=Olenick |first1=Doug |title=BrickerBot creators announce retirement from active operations |url=https://www.scmagazine.com/brickerbot-creators-announce-retirement-from-active-operations/article/713576/ |website=SC Media US |access-date=August 4, 2018 |language=en |date=12 December 2017}} US-CERT released an alert regarding BrickerBot on April 12, 2017.{{cite web|title=BrickerBot Permanent Denial-of-Service Attack (Update A) {{!}} ICS-CERT|url=https://ics-cert.us-cert.gov/alerts/ICS-ALERT-17-102-01A|website=ICS-CERT|date=April 18, 2017 |access-date=February 26, 2018|language=en}}
References
{{reflist}}
{{IoT Malware}}
{{Hacking in the 2010s}}