PDoS is an attack that harms a system so severely that it requires substitution or re-installation of hardware.By abusing security defects or misconfigurations, PDoS can decimate the firmware or potentially functions of system.
Attack classified into two stages.
- BrickerBot.1 – short-lived bot.
- BrickerBot.2 – Bot that initiates PDoS attempts.
BrickerBot Attacking Vector
BrickerBot uses traditional Brute force method to initiate the attack, upon successful mitigation it runs a series of LINUX commands.
Which leads to corrupted storage, trailed by commands to disturb Internet network, device execution, and then wiping of all records on the device.
In parallel, Radware’s honeypot recorded more than 333 PDoS endeavors with an alternate command signature. The source IP addresses from these endeavors are TOR Nodes and subsequently there is no recognizing the real wellspring of the attacks.
It is significant that these attacks are as yet progressing and the attacker/creator is utilizing TOR egress hubs to cover its bot(s).The first credentials attempted to brute the Telnet login are root/root and root/vizxv.
The utilization of the “busybox” command combined with the MTD and MMC extraordinary devices implies this attack is focused on particularly at Linux/BusyBox-based IoT devices.
PDoS endeavors started from a predetermined number of IP locations spread the world over. All devices are exposing port 22 (SSH) and running very older version of the Dropbear SSH server.
- Change the device’s factory default credentials.
- Disable Telnet access to the device.
- Network Behavioral Analysis can detect anomalies in traffic and combine with automatic signature generation for protection.
- User/Entity behavioral analysis (UEBA) to spot granular anomalies in traffic early.
- An IPS should block Telnet default credentials or reset telnet connections. Use a signature to detect the provided command sequences.