Skip to content
Post Mortem

Biggest cases ยท September to October 2016

Mirai and Dyn: smart cameras that broke half the internet

A botnet made of hijacked cameras and home routers knocked out a company that translates website names, and with it Twitter, Reddit, Netflix, GitHub and more for many users.

HIGHddosiotdnsdefault-passwords

Details may change as reporting changes. Information comes from the linked sources, and we do not guarantee it is complete or current.

Why it is on the listIt was one of the largest disruptions of everyday internet services, caused by gadgets with factory-default passwords.

In plain English

DNS is the internet's phone book. When you type a website's name, DNS tells your device where to find it. Dyn ran DNS for many big sites. If Dyn is down, the sites are still running, but your device cannot find them.

A program called Mirai searched the internet for cameras, routers and recorders that still used the password they shipped with. It took them over, then pointed them all at Dyn at once.

The owners of those devices did not notice anything. Their camera just worked as usual.

Words used here

DNS
The internet's phone book that turns a name like example.com into an address.
IoT
Internet-connected gadgets such as cameras, baby monitors and smart plugs.
Default password
The login a device ships with. If nobody changes it, anyone can look it up.

What happened

On October 21, 2016, Dyn's managed DNS service came under attack in waves. Many users could not reach well-known sites for hours.

Dyn said Mirai-based botnets were the primary source of the traffic and estimated about 100,000 infected devices. Early press estimates were much higher.

Mirai's code had been published online a few weeks earlier, which let many others copy it.

How it unfolded

  1. Late September 2016

    Mirai's source code is released after earlier large attacks.

  2. October 21, 2016, morning

    First wave against Dyn. Major sites become hard to reach.

  3. Several hours later

    A second wave. Dyn and partners filter traffic and services recover.

Who was affected

Millions of people trying to use many popular services, mostly in the US and Europe, plus businesses that relied on Dyn alone for DNS.

What the response was

  • Dyn filtered traffic and worked with partners to absorb it.
  • Customers added backup DNS providers.

What went wrong

  • Many devices shipped with passwords nobody could change, or nobody did.
  • Many sites depended on a single DNS provider.

What worked

  • The provider and its partners kept the service recoverable within hours.

What organisations should do differently

  • Change the default password on every gadget when you set it up.
  • Use two DNS providers for anything important.
  • Do not expose cameras and admin pages directly to the internet.

What you can do today

  • Change the admin password on your router and any camera or recorder.
  • Update their firmware, and switch off remote access you do not use.
  • If you run a website, check whether it relies on a single DNS provider.

The lesson that still holds

Small, boring devices can add up to a large weapon. Change defaults, keep things updated, and do not rely on a single provider for something everything else depends on.

Sources

Finished this one?

Add it to What I learned and earn 40 Trust. You can open your list from the badge at the bottom of the page.