IoT botnet launched massive 13-day DDoS attack against streaming service

Can you put your hand on your heart and say the web application your company has built would be able to handle 292,000 requests per second, from 402,000 different IP addresses?

A denial-of-service attack of that magnitude would be hard for many services to stand up against, regardless of how well they had been built, the security best practices that had been followed, the penetration tests that they had survived.

Yet, according to a new report from DDoS mitigation firm Imperva, one company was targeted with just that size of attack earlier this spring.

The company, which is unnamed, but said to produce an entertainment streaming app, was the subject of a massive Application Layer 7 DDoS attack starting in later April.

For nearly two weeks the DDoS attack was consistently over 100,000 requests per second, peaking at 292,000 requests per second.

Imperva described it as the largest Layer 7 DDoS attack it had ever seen.

Application Layer 7 DDoS attacks differ from network layer DDOS attacks that aim to congest communication between a targeted site and the rest of the internet, gobbling up as much bandwidth as possible. Instead Layer 7 DDoS attacks attempt to mimic normal user behaviour, consuming resources on a web server by flooding a web with a large number of HTTPS GET/POST requests.

Such traffic can be difficult to tag as malicious, as it can be hard to differentiate from legitimate user activity.

As a result, Layer 7 DDoS attacks can be more difficult to defend against – although Imperva says it was able to mitigate the attack and its customer, thankfully, suffered no downtime.

However, in their investigation into the attack researchers pointed a finger of suspicion at IoT devices, infected with a version of the Mirai malware.

Mirai made headlines in 2016, after a devastating DDoS attack was launched at the Dyn domain name service, disrupting access to some of the world’s most popular websites.

Mirai created a huge botnet by scanning huge swathes of the internet, searching for open Telnet ports, and attempted to gain access to devices via Telnet through the simple trick of trying weak usernames and passwords.

With sad predictability, it was shown that owners of vulnerable IoT routers and webcams had failed to learn that using a default username and password on an internet-enabled device was about as good as having no password at all.

It doesn’t appear that it was the original Mirai botnet that attacked the unnamed entertainment company, but instead one of the many Mirai variants which emerged after the source code for Mirai was made available for download.

The release of that code made it that little bit easier to hijack CCTV cameras, routers, and all manner of other IoT devices to bombard websites with attacks, including this latest Layer 7 DDoS attack.

Analysis of the IP addresses that performed the attack revealed that the majority of them, by far, were based in Brazil.

In an attempt to evade interception by DDoS mitigation services, the attackers used a legitimate User-Agent in order to appear to look the same as queries by a legitimate streaming app.

And, although it has been hard to confirm, it is thought that the motivation for the attack may have been to break into accounts using credential stuffing and brute force techniques.

As IoT botnets continue to be harnessed to launch damaging DDoS attacks it becomes more important than ever for consumers to ensure that their internet-connected gadgets are properly secured and patched.

After all, you don’t want to be partly responsible for one of the biggest Layer 7 DDoS attacks in history, do you?

 

One comment

  • By coyote - Reply

    Nitpicking: In one place you have the abbreviation all caps when it should be (as you have elsewhere) DDoS.

    And …. telnet? It’s sad that that any telnetd runs on any device. Yet medical devices (also connected to the Internet – beyond disgraceful) have been compromised over telnet. Did I say ‘compromise’? Sorry I meant logged into not only without authorisation required but root access. That’s not ‘compromised’ at all. That’s not security at all. That’s pointless. It’s absolutely insane. Yet it’s something that is unfortunately reality. So too is keeping default passwords of course… Or weak stupid passwords whether or not they’re in the huge password list files. And not having proper ingress filtering. And … list goes on and on and on.

    To think though: in the early 2000s the 13 year old Canadian who called himself ‘MafiaBoy’ executed up to that point one of the if not the most serious DoS attacks (and I believe it was one of the first DDoS attacks but I’m vague on that now) up to that point. As I recall he took down Amazon and eBay and maybe even some DNS servers (root) though I’m not sure on the last one. Yet if we look back at that it’s nothing at all. Arguably the old smurf/fraggle from the 1990s (written by the programmer who called himself TFreak – and no I have no idea how I remember those details I just do) was (fraggle was over UDP but otherwise the same) a DDoS attack due to the fact it was a broadcast attack. Yet it had a silver lining in that it was one of the contributing factors of updated RFCs which suggest that hosts should be far more strict on what would be allowed with the bcast of a network.

    Yet what we see these days makes those look like DoS attacks that target a single host for maybe an hour or two at most. Scary yes. But what’s far scarier is it’s only going to get worse and it seems to me exponentially worse at that.

  • Add Comment

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