Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint

4/7/2017
09:00 AM
50%
50%

New Malware Deliberately Destroys Unsecured IoT Devices

Motive behind BrickerBot puzzles experts who think it maybe the work of a vigilante.

Cybersecurity experts are warning of a new type of malware strain that uses known default user credentials to attack unsecured Internet of Things (IoT) devices and destroy them, reports Bleeping Computer.

Discovered by cybersecurity firm Radware, BrickerBot has two versions – BrickerBot.1 and BrickerBot.2 – and was found to be active since March 20, targeting only Linux BusyBox-based devices with Telnet ports left open.

This malware renders devices inoperable within seconds of infecting them through PDoS (Permanent Denial of Service) or "phlashing" attacks. The two versions work in the same manner but through different sets of commands; while BrickerBot.1 comes through worldwide IPs likely assigned to Ubiquiti network devices, BrickerBot.2 attacks are hidden behind Tor exit nodes and difficult to trace.

The attacker’s motive has confounded cybersecurity experts because it destroys without benefiting the destroyer. They suspect it could be the work of a vigilante who wants to alert users to unsecured devices.

Victor Gevers of GDI.foundation is however critical of the approach and believes that, "Instead of bricking you could also allow the devices to still work and just patch the vulnerability.”

Click here for details.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
JesseP882
50%
50%
JesseP882,
User Rank: Apprentice
4/8/2017 | 7:34:58 PM
You cant fix stupid
Look, I understand the perspective that as people in IT Security we should make it our buisness to fix everyones issue. But you can't fix stupid nor can you protect everyone from themselves. Sorry Victor Gevers. But even in law enforcement, you can put as many fixes (checkstops) in place as possible, work to get laws setup and rules. But when someone decides to get drunk then drive behind the wheel, even police cannot stop every idiot drunk from killing innocents.

This malware, while appearing to be malicious in nature, is truly epic. No one is hurt, besides the victims pockbook/wallet, and nothing is gained from the attack. And the only true lesson learned here is this: Change the default password.

 

Awesome! And if buddy goes, gets new hardware and then refuses to change the password which again results in another infection and bricking of hardware again.... Sucks to be him.

What can we do? We cannot protect against stupid. Only educate and inform. We could be dictators. But then we would be no better than Microsoft was back in the day or Apple when the systems were locked down to prevent mods. So important lessons need to be learned. Always change the default password. Failure to do so will result in your own monetary loss due to your own idiocy.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/7/2017 | 2:31:11 PM
Push in the right direction
Hopefully this will push vendors in the right direction to not supply their devices with default credentials.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/5/2020
How AI and Automation Can Help Bridge the Cybersecurity Talent Gap
Peter Barker, Chief Product Officer at ForgeRock,  6/1/2020
Cybersecurity Spending Hits 'Temporary Pause' Amid Pandemic
Kelly Jackson Higgins, Executive Editor at Dark Reading,  6/2/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13868
PUBLISHED: 2020-06-05
An issue was discovered in the Comments plugin before 1.5.5 for Craft CMS. CSRF affects comment integrity.
CVE-2020-13869
PUBLISHED: 2020-06-05
An issue was discovered in the Comments plugin before 1.5.6 for Craft CMS. There is stored XSS via a guest name.
CVE-2020-13870
PUBLISHED: 2020-06-05
An issue was discovered in the Comments plugin before 1.5.5 for Craft CMS. There is stored XSS via an asset volume name.
CVE-2020-5591
PUBLISHED: 2020-06-05
XACK DNS 1.11.0 to 1.11.4, 1.10.0 to 1.10.8, 1.8.0 to 1.8.23, 1.7.0 to 1.7.18, and versions before 1.7.0 allow remote attackers to cause a denial of service condition resulting in degradation of the recursive resolver's performance or compromising the recursive resolver as a reflector in a reflectio...
CVE-2020-10071
PUBLISHED: 2020-06-05
The Zephyr MQTT parsing code performs insufficient checking of the length field on publish messages, allowing a buffer overflow and potentially remote code execution. NCC-ZEP-031 This issue affects: zephyrproject-rtos zephyr version 2.2.0 and later versions.