United States: The Evolution Of Mirai Botnet Source Code Presents Increased Risk Of Large-Scale DDoS Attacks

Last Updated: September 5 2018
Article by Cooley LLP

Over the past few years, several major distributed denial-of-service ("DDoS") attacks took place, including a major event affecting the domain name service provider Dyn, which caused outages and slowness for a number of popular sites, including Amazon, Netflix, Reddit, SoundCloud, Spotify, and Twitter. However, since several of these large, highly-publicized attacks occurred in 2016, there have been new developments that provide insight into some of the current trends and risks that companies face today relating to these DDoS Attacks. Most recently, several security firms have identified the evolution of the source code used in the Mirai botnet that significantly expand its power by allowing more devices to be commandeered. In this post we delve into this threat vector and how it may impact organizations.

At their most basic level, DDoS attacks work by sending a high volume of data from different locations to a particular server or set of servers. Because the servers can only handle a certain amount of data at a time, these attacks overwhelm the servers causing them to slow significantly or fail altogether. This prevents authorized users from being able to use or access the services being provided via the attacked servers. DDos attacks are particularly problematic for companies because they can result in direct revenue losses if customers are unable to transaction.

The 2016 Mirai Malware and Attacks

In 2016, several sizeable attacks were attributed to a malware variant named Mirai, which commandeered various internet-enabled digital video recorders (DVRs), cameras, and other IoT devices and was then utilized by attackers to launch multiple high-profile, high-impact DDoS attacks against various Internet properties and services.

This botnet was particularly effective based on the increasing prevalence of Internet of Things (IoT) devices. Researchers estimate that over 23 billion IoT devices are installed globally in 2018 (and that number is expected to rise to 75 billion by 2025). The attackers are able to exploit the relative security weaknesses in IoT devices by using malware to create networks of these computers, known as botnets, which report to a central control server that can be used as a staging ground for launching powerful DDoS attacks. Due to the enormous number of IoT devices that can be compromised simultaneously, the amount of traffic an attacker could generate by using a botnet "army" is far more substantial than the DDoS attacks of the past.

Mirai operated primarily as a "DDoS-for-hire" service in which attackers launch DDoS attacks against a target in exchange for payment, generally made in Bitcoin. These Mirai-based attacks were successful in creating extensive outages and the method for gaining control over the IoT devices was relatively straightforward—relying on using weak or default passwords on these IoT devices. The source code for Mirai was released publicly in 2016, which, as predicted, lead to more of these attacks occurring and a continuing evolution of the source code.

In 2017, researchers identified a new IoT botnet, named IoT Reaper or IoTroop, that built on portions of Mirai's code. Instead of exploiting passwords of the devices it infects, the new botnet uses known security flaws in the code of those insecure devices to take control of them and then searches for other vulnerable devices to spread itself further. Vulnerable devices include various routers made by leading manufacturers, such as D-Link, Netgear, and Linksys, in addition to the types IoT devices used by Mirai.

The Next Generation of Marai Variants

Earlier this year, researchers identified attempts to further refine the Mirai source code, which was posted publicly in 2016. Researchers from Netscout's Arbor Security Engineering and Response Team (ASERT) identified that botnet authors are using the Mirai source code as a framework, but then adding in new exploits and functionally, thus dramatically decreasing the development time for botnets. Furthermore, these botnets are then being used not only to launch DDoS attacks, but for other purposes as well, including attacks on cryptocurrency mining clients. Specifically, researchers have identified the following four Mirai variants: Satori Botnet, Masuta Botnet, Wicked Mirai, and JenX botnet, each of which is described in further detail below.

Satori Botnet

The Satori Botnet is a variant of Mirai that targets software associated with ARC processors, which are used in a variety of IoT devices. Once it finds a vulnerable IoT device, Satori performs a check to determine whether the device's default settings have been changed, and, if not, uses these default credentials to gain control of the device. Once a device has been compromised, it searches for other devices on the network and attempts to repeat this process.

Most recently, researchers have identified that Satori-controlled devices were mass-scanning the Internet for cryptocurrency-mining devices that were exposed to the internet. Once under control, the attackers would push instructions to reconfigure the compromised device to join a mining pool and deposit earned cryptocurrency into the attacker's wallet.

Masuta

Masuta comes in two variants, Masuta Botnet, which uses the same techniques as Mirai by attempting to overcome the security of the target IoT devices using a built-in list of common passwords and default credentials, and PureMasuta, which has been described as "an enhanced version" with a built-in exploit against certain vulnerable routers. Masuta is believed to be the work of the same group responsible for developing the Satori Botnet, however unlike Satori, Masuta attacks allow the actors to take direct control of compromised devices, making other malicious actions possible, including:

  • Trojan Activity — Using embedded code to launch a Trojan virus onto the target IoT devices, allowing the attacker to view device activity in real time as well as take over control of the machines at any given time.
  • Traffic Redirect Activity— Using compromised networking gateway equipment (such as routers and switches) the attackers reroute internet traffic through a server they control, enabling complex man-in-the-middle attacks.
  • Malware Delivery — Using the compromised device to deliver various types of viruses to other connected devices on the network.

Wicked Mirai

The Wicked iteration of Mirai contains a package that includes at least three exploits. This variant scans multiple ports on network devices, and uses open ports to download copies of various payloads (the nature of the payload will depend on which ports are available). Unlike Mirai, however, which used brute force to gain access to vulnerable IoT devices, the Wicked version relies on a variety of port-related vulnerability exploits, some new and some very old, to gain access to a device.

Once on a system, Wicked Mirai contacts a command and control server from which it downloads a payload (in some cases payloads from other Mirai variants like Sora, Owari, and Omni) that can vary based on the attackers' objective and the nature of the affected device. Wicked looks for specific vulnerabilities on a platform that the botnet can exploit. This change allows the botnet controllers to have a faster compromise time, which allows the botnet to come online faster. In addition, the Wicked variant is also able to maintain a presence on IoT devices it infects beyond the occasional reboots, increasing its power and persistence to launch substantial DDoS attacks.

JenX Botnet

The JenX variant is a unique variant that leverages the Grand Theft Auto videogame community to infect IoT devices. Unlike the Satori and Masuta variants, JenX has a centralized infrastructure and uses a central server to perform the scanning of new hosts. The other variants perform distributed scanning and exploiting (e.g., each compromised device searches for new victims), facilitating rapid growth of the botnet, but that comes at the price of flexibility and sophistication. The centralized structure of JenX provides the attackers with greater flexibility to add and improve the functionality of the malware over time. This variant was advertising DDoS attacks as a service with a guaranteed bandwidth of 290 to 300 Gbps for the attack, which the attackers explained would employ "God's wrath . . . against the IP that you provide us."

Next Steps

With the increasing threat of these attacks, coupled with the number of different ways that they can be leveraged, organizations should take steps to prepare for, respond to, and mitigate some of the potential fall-out associated with a DDoS or other botnet attack. Outlined below are some of the steps that organizations can consider to mitigate their exposures before, during, and after such an attack.

Before an Attack

  • Incident Response Planning. As with any potential security incident, effective planning can help reduce or eliminate some of the potential business harms and legal consequences before an attack occurs. Companies should incorporate emergency situations like DDoS or ransomware attacks, which have the propensity to affect critical business operations, in their Incident Response Plans (IRP). E-commerce companies and others that rely heavily on website traffic may wish to identify "mission critical" resources and devise alternative solutions that can be used in the event of website failure following a DDoS attack.
  • Negotiating/Reviewing Contractual Liability. Losses of service could affect an organization's contractual obligations; for example, unavailability of resources may impact uptime and reliability guarantees contained in service-level agreements or other similar contract provisions. Contracting parties should be certain to consider and address these issues during the contract negotiation process to ensure that the risks associated with these incidents are properly allocated between or among the parties involved. For example, organizations may wish to address the potential repercussions from a DDoS in various contractual provisions:

    • Revising force majeure provisions or other exceptions to contractual service guarantees to exclude downtime attributable to these type of incidents from uptime or reliability calculations;
    • Creating disclaimer or limitation of liability language in agreements that expressly limits or eliminates potential liability associated with the inability to perform transactions during a system or website outage;
    • Carefully drafting security incident notification clauses to avoid contractual liability where notice might be required under a contract, but would not be required under any other law or regulation; and
    • Allocating risk and liability for potential outages in terms governing limitations on liability and indemnity.
  • DDoS Mitigation. Organizations should consider retaining third parties to provide DDoS mitigation services designed to combat these attacks by absorbing or deflecting DDoS traffic. Companies already using these services may wish to review the level of services provided to ensure that they have an adequate amount of protection in light of the increasing data volume seen in recent IoT-based attacks. Historical levels of protection may be insufficient in light of the increasing numbers of IoT devices that are becoming more easily exploitable.
  • Documenting Security and Preventative Measures. In anticipation of potential litigation and regulatory enforcement, we recommend that organizations document the various security measures that are being implemented, including those designed to prevent and mitigate the effects of cyber attacks. Documenting security practices and decisions as they are being designed can help bolster arguments that a companies' actions were reasonable under the circumstances. Although, in the context of litigation or a regulatory investigation, these actions will be viewed in hindsight by a court, jury, or regulator, contemporaneous information about these can significantly bolster defenses against claims of negligence or breach of contract by litigants or non-compliance by regulators and may also help defend against litigation.

During an Attack

  • Establishing and Preserving Attorney-Client Privilege. A key consideration in the investigation of and response to any cyber incident is establishing and preserving attorney-client privilege or work-product doctrine protections. Important steps in preserving privilege include: (i) retaining or involving legal counsel early in the process, (ii) focusing the investigation on providing legal advice to the organization, including providing legal advice in anticipation of litigation and regulatory inquiries, and (iii) retaining forensic or security experts through legal counsel.
  • Balancing Remediation and Investigation Objectives. Unfortunately, remediating an attack and restoring operations may adversely impact evidence needed to investigate an incident. We recommend that organizations confer with forensic experts and legal counsel as soon as possible following the start of an attack to gauge how containment and remediation could affect important evidence.
  • Involving Law Enforcement. Organizations often reflexively want to contact law enforcement in response to a data incident. Although this may be beneficial, there are some considerations that organizations should weigh before doing so. The frequency and severity of these attacks has led to more attention from various law enforcement agencies and significantly more success in identifying and prosecuting attackers. Federal law enforcement agencies often have intelligence on various groups responsible for these attacks and, as a result, may be able to provide important information in responding to, containing, and remediating these attacks. However, law enforcement agencies may not always be able to share much information, particularly where the information relates to an ongoing investigation.

Additionally, alerting law enforcement can result in having the agency become significantly more involved in, or even controlling, the investigation of the incident. Law enforcement involvement could impact privilege issues and, more generally, may not be ideal in all circumstances. We suggest that organizations consult with legal counsel to evaluate the potential advantages and disadvantages of notifying law enforcement based on their specific circumstances.

  • DDoS Mitigation. Companies should be aware that many DDoS mitigation vendors offer emergency DDoS hotlines or protection services that can be deployed for new customers, even where a company has not proactively secured such services. Engaging a DDoS mitigation service provider after an attack has started can help to reduce the length and severity of an attack, allowing a company to get its affected servers and websites back up and running more quickly.

After an Attack

  • External Communications. When and how an organization communicates about a DDoS or other cyber attack may impact its exposure and liability following an incident. These communications may include: (i) general communications about the incident with media, investors, customers, or regulators; and (ii) formal notifications ranging from those necessitated by legal or regulatory requirements to formal contractual notices necessary to exercise force majeure or emergency circumstances. Organizations should be especially cautions about all internal and external communications and we suggest that organizations consult with legal counsel, and in some cases external public relations resources, to more fully evaluate the potential effects such communications may have on the investigation and the organization more generally.
  • Further Investigation. Following an organization's remediation and restoration efforts, it is often necessary to conduct a further investigation into the circumstances surrounding the attack and to determine whether and to what extent any legal obligations have been triggered. Depending on the organization's capabilities and resources, it may be possible to leverage any incident detection measures the organization has to identify indicators of compromise and confirm that the malicious activities were limited to the known aspects of the particular attack. In some circumstances, retaining independent forensic investigators may be necessary to conduct a thorough investigation into whether any unauthorized access or acquisition to customer information or confidential business information occurred prior to or during the attack.
  • Preparing for Potential Litigation or Claims. As mentioned previously, DDoS attacks could result in litigation or regulatory scrutiny for a variety of reasons. Examples of potential actions stemming from such an attack include:

    • An action brought by financial services customers alleging consequential damages and lost profits based on an inability to access financial accounts or buy and sell stock during an attack;
    • Claims against service providers for failing to provide contractually-guaranteed service levels;
    • Claims based on allegations of the theft of customer information, trade secrets, intellectual property, or other confidential or protected information; and
    • Claims alleging negligence or fraud based on a company's failure to adequately protect against a DDoS attack or appropriately limit liability in its agreements with customers.

Anticipating and preparing for this type of potential exposure can better position the organization for defending against these claims. Relatedly, organizations are required to preserve potentially relevant information and documents once they reasonably anticipate litigation. To that end, organizations should consult with legal counsel to determine when it is appropriate to put litigation holds in place to ensure that they avoid potential spoliation issues and sanctions. Organizations in this position must also consider whether and how an assertion of privilege protections under the work-product doctrine may affect its preservation obligations. If a company asserts that materials have been prepared by and with legal counsel "in anticipation of litigation" and are therefore protected, it should consider whether this assertion also triggers an obligation to preserve evidence at that time.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
Similar Articles
Relevancy Powered by MondaqAI
Lewis Brisbois Bisgaard & Smith LLP
 
In association with
Related Topics
 
Similar Articles
Relevancy Powered by MondaqAI
Lewis Brisbois Bisgaard & Smith LLP
Related Articles
 
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Registration (you must scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these Terms or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.

Disclaimer

The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of the Content or performance of Mondaq’s Services.

General

Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions