BrickerBot Author Claims Responsibility for Indian Cyberattack
The creator of the BrickerBot malware claimed credit for a cyberattack that caused over 60,000 internet outages in India from July 25 to July 29, 2017, Bleeping Computer reported.
The two companies affected were Bharat Sanchar Nigam Limited (BSNL) and Mahanagar Telephone Nigam Limited (MTNL), which are both state-owned telecommunications service providers. The malware also affected routers that were part of BSNL’s National Internet Backbone (NIB). Fortunately, these NIB routers were brought back up quickly, but thousands of users were without internet connectivity for an extended period of time.
Reset Modems Still Vulnerable to Attack
According to Bleeping Computer, BSNL said that the malware affected modems that had their default passwords enabled, and advised users to change them. But one local newspaper, The Hindu, reported that the reset modems were still vulnerable to the malware, even with new passwords.
The previously seen BrickerBot malware infects Linux-based Internet of Things (IoT) and networking devices. It does not turn devices into botnets for distributed denial-of-service (DDoS) attacks but bricks the equipment by directly rewriting its flash storage. Sometimes this is reversible, sometimes it is not.
BrickerBot Author Emerges
Over the weekend, the BrickerBot author told Bleeping Computer in an email that he was the author of the malware. Further, he blamed the cause of the attack on BSNL and MTNL, and claimed that he developed and spread the malware to make internet service providers (ISPs) aware that unsecured devices should be safeguarded against bricking.
The author told Bleeping Computer that “BSNL’s devices are generally insecure, and BSNL isn’t being honest about the situation by blaming its customers for negligence.”
Painting himself as a cybervigilante, he also told the source, “They have hundreds of thousands of modems with unprotected TR069 (TR064) interfaces, which allow anybody to reconfigure the devices for MitM attacks or DNS hijacking. There isn’t much that an affected customer can do to prevent such attacks since the BSNL network and its devices are insecure by design.”
Filtering Port 7547 Ends Attacks
The author said that the cause of the attack was that the ISPs were allowing external connections into their network via port 7547. This is the port that is used by TR069, which is a protocol often leveraged by ISPs to send commands and manage routers at a user’s location. Such external connections could easily be misused.
Both of the affected providers limited access to port 7547 over the weekend, and the situation quieted down. While this malware seems to have been reversible, not all cases are, and users must take advantage of every security control offered to ensure they don’t become victims in the future.