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

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.
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: just wondering...Thanx
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.