<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.bharatpedia.org/w/index.php?action=history&amp;feed=atom&amp;title=BrickerBot</id>
	<title>BrickerBot - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://en.bharatpedia.org/w/index.php?action=history&amp;feed=atom&amp;title=BrickerBot"/>
	<link rel="alternate" type="text/html" href="https://en.bharatpedia.org/w/index.php?title=BrickerBot&amp;action=history"/>
	<updated>2026-08-06T08:15:47Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.6</generator>
	<entry>
		<id>https://en.bharatpedia.org/w/index.php?title=BrickerBot&amp;diff=430178&amp;oldid=prev</id>
		<title>Ajay Kumar: Created a new article</title>
		<link rel="alternate" type="text/html" href="https://en.bharatpedia.org/w/index.php?title=BrickerBot&amp;diff=430178&amp;oldid=prev"/>
		<updated>2023-09-25T18:38:28Z</updated>

		<summary type="html">&lt;p&gt;Created a new article&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{short description|Destructive malware targeting IoT devices}}&lt;br /&gt;
{{use mdy dates |date=December 2020}}&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;BrickerBot&amp;#039;&amp;#039;&amp;#039; was [[malware]] that attempted to [[Denial-of-service_attack#Permanent_denial-of-service_attacks|permanently destroy]] ([[Brick (electronics)|&amp;quot;brick&amp;quot;]]) 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.&lt;br /&gt;
&lt;br /&gt;
The most infected devices were in Argentina, followed by North America and Europe, and Asia (including India).&amp;lt;ref&amp;gt;{{cite web |title=BrickerBot: &amp;quot;The Doctor&amp;#039;s&amp;quot; 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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Discovery ==&lt;br /&gt;
&lt;br /&gt;
=== BrickerBot.1 and BrickerBot.2 ===&lt;br /&gt;
The BrickerBot family of malware was first discovered by [[Radware]] on April 20, 2017, when BrickerBot attacked their [[Honeypot (computing)|honeypot]] 1,895 times over four days. BrickerBot&amp;#039;s method of attack was to brute-force the [[telnet]] password, then run commands using [[BusyBox]] to corrupt [[MultiMediaCard|MMC]] and [[Memory Technology Device|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)|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.&amp;lt;ref&amp;gt;{{cite web|title=&amp;quot;BrickerBot&amp;quot; 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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== BrickerBot.3 and BrickerBot.4 ===&lt;br /&gt;
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.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Shutdown and Impact ==&lt;br /&gt;
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.&amp;lt;ref&amp;gt;{{cite web |last1=Shattuck |first1=Justin |title=BrickerBot: Do &amp;quot;Good Intentions&amp;quot; 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}}&amp;lt;/ref&amp;gt; In an interview with &amp;#039;&amp;#039;[[Bleeping Computer]]&amp;#039;&amp;#039;, Janit0r stated that BrickerBot was intended to prevent devices from being infected by [[Mirai (malware)|Mirai]].&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt; [[US-CERT]] released an alert regarding BrickerBot on April 12, 2017.&amp;lt;ref&amp;gt;{{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}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
{{reflist}}&lt;br /&gt;
&lt;br /&gt;
{{IoT Malware}}&lt;br /&gt;
{{Hacking in the 2010s}}&lt;br /&gt;
&lt;br /&gt;
[[Category:IoT malware]]&lt;br /&gt;
[[Category:Cybercrime in India]]&lt;/div&gt;</summary>
		<author><name>Ajay Kumar</name></author>
	</entry>
</feed>