Mirai Botnet

Talking about something that had created history, Mirai Botnet is one of this kind. Mirai (Japanese for “the future”) is a tremendously malicious malware that attacks Linux driven systems and cause (DDos) distributed denial of services. DDos is all about services jam on an extensive level and attacker uses more over one to thousands of inimitable IP addresses. The specific attacks happen to IoT (Internet of Things) that are essentially internetworking of physical devices, vehicles (also referred to as “linked devices” and “smart devices”).

Investigators following Mirai say that while the number of daily attacks dipped briefly, they’re now observing development in the Mirai malware itself that appears designed to allow it to contaminate more of the vulnerable routers, DVRs and other internet-of-things (IoT) devices it’s hijacked to power its streams of malicious traffic. That development could actually increase the total population available to the botnet, they warn, potentially giving it more total compute power to draw on. Mirai botnet is becoming very popular in the illegal underground.

According to resources, in august 2015 a research company MalwareMustDie caught Mirai malware in a Linux driven device for first time. They were basically running a Linux Trojan test and detected Mirai malware. The specialists highlighted that to determine a Mirai infection, it was vital to analyze memory of the compromised gadgets because the examination led from the file system or from the external network traffic doesn’t give any evidence, at the beginning. The Mirai botnet has infected hundreds of thousands of Internet of Things (IoT) devices, specifically security cameras, by using vendor default passwords for Telnet access. Since its inception, the Mirai ‘Internet-of-Things’ (IoT) botnet, comprised largely of  Internet-enabled digital video recorders (DVRs), surveillance cameras, and other Internet-enabled embedded devices, has been used by assailants to launch numerous high-profile, high-impact DDoS attacks in contradiction of many Internet properties and facilities.  While the original Mirai botnet is still in active use as of this writing, multiple danger actors have been experienced customizing and improving the attack competences of the innovative botnet code, and additional Mirai-based DDoS botnets have been observed in the wild.

The original Mirai botnet (henceforth referred to as ‘the Mirai botnet’, or ‘Mirai’, unless otherwise indicated) presently contains of a floating population of approximately 500,000 compromised IoT devices worldwide; relatively high concentrations of Mirai nodes have been observed in China, Hong Kong, Macau, Vietnam, Taiwan, South Korea, Thailand, Indonesia, Brazil, and Spain.  Additional Mirai concentrations have been also been observed in multiple countries located in North America, Europe, and Oceania.

Attacks and details:

  • Mirai was used in the DDoS attack on 20 September 2016 on the Krebs on Security site which reached 620 Gbps. Ars Technica also stated a 1 Tbps attack on French web host OVH (OVH is an Internet Service Provider providing dedicated servers, shared and cloud hosting, domain registration, and VOIP telephony services.).
  • On 21 October 2016 multiple major DDoS attacks in DNS services of DNS service provider Dyn, Inc. occurred using Mirai malware installed on a large number of IoT devices, resulting in the inaccessibility of several high profile websites such as GitHub, Twitter, Reddit, Netflix, Airbnb and many others. The attribution of the attack to the Mirai botnet was originally reported by BackConnect, a security firm.
  • Staff at Deep Learning Security observed the steady growth of Mirai botnets before and after the 21 October attack.
  • Mirai has also been used in an attack on Liberia’s Internet infrastructure in November 2016. According to computer security expert Kevin Beaumont the attack appears to have originated from the actor which also attacked Dyn, Inc.

 

Recent Posts

Recent Comments

    Archives

    Be First to Comment

    Leave a Reply

    Your email address will not be published. Required fields are marked *