Thursday, December 26, 2024
HomeDDOSLargest Layer 7 DDOS Attack Recorded By Google with 46 Million Requests...

Largest Layer 7 DDOS Attack Recorded By Google with 46 Million Requests Per Second

Published on

SIEM as a Service

Google has been targeted with the largest DDoS attack in history against one of its customers. An attack on one of the Google Cloud Armor customers occurred on June 1st, during which 46 million requests were sent per second to a Google Cloud Armor customer by HTTPS DDoS attacks. 

It is the most powerful Layer 7 DDoS attack that has ever been reported to date, it has surpassed the previous record by at least 76%. 

It would be equivalent to receiving all of the daily requests to Wikipedia in just a few seconds, so you can get a sense of the scale of the attack.

- Advertisement - SIEM as a Service

By detecting and analyzing the traffic early in the attack cycle, Cloud Armor Adaptive Protection was able to prevent the attack from succeeding. 

A protective rule was recommended by Cloud Armor to the customer, which was delivered to the customer before the attack reached its full extent. 

With the assistance of Cloud Armor, the customer’s service was kept online, and its end users were able to continue receiving services.

Long-lasting assault

The incident happened around 09:45 Pacific Time on June 1st and is believed to be a web-based attack. In an attempt to compromise the victim’s HTTP/S load balancer, the attacker had initially been able to generate only 10,000 requests per second.

There was an increase of 100,000 RPS within eight minutes of the attack starting. Upon receiving specific data pulled from Google’s traffic analysis, Cloud Armor Protection generated an alert and a signature that kicked in based on the data.

There was a peak of 46 million requests per second two minutes later as a result of the attack. Thanks to Cloud Armor’s recommendation, the customer had already deployed the rule to enable normal operation. In the 69 minutes that followed the start of the assault, the assault came to an end.

This alert included a recommendation for a rule that can be used to block signatures with malicious intent.

In total, 5,256 source IP addresses were involved in the attack, originating from 132 countries around the world. Around 31% of the total attack traffic was generated by the top 4 countries.

There is still no information about the malware that is behind this attack. Mēris botnet appears to be the most likely provider of these services based on the geographical distribution of their use.

The use of Tor exit nodes as the delivery mechanism for the traffic is another characteristic of this attack. A significant amount of unwanted traffic can be delivered via Tor exit nodes, according to Google researchers.

Moreover, there will be continued growth in the size of the attack and evolution in tactics in the next few years. So, users should deploy robust security mechanisms to defend and mitigate such attacks.

Also Read: The Rise of Remote Workers: A Checklist for Securing Your Network – Free E-Book Download

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Researchers Uncovered Dark Web Operation Acquiring KYC Details

A major dark web operation dedicated to circumventing KYC (Know Your Customer) procedures, which...

Adobe Warns of ColdFusion Vulnerability Allows Attackers Read arbitrary files

Adobe has issued a critical security update for ColdFusion versions 2023 and 2021 to...

Beware of New Malicious PyPI packages That Steals Login Details

Two malicious Python packages, Zebo-0.1.0 and Cometlogger-0.1, were recently detected by Fortinet's AI-driven OSS...

Brazilian Hacker Arrested Hacking Computers & Selling Data

A Brazilian man, Junior Barros De Oliveira, has been charged with multiple counts of...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Over 300,000 Prometheus Servers Vulnerable to DoS Attacks Due to RepoJacking Exploit

The research identified vulnerabilities in Prometheus, including information disclosure from exposed servers, DoS risks...

Europol Shutsdown 27 DDoS Service Provider Platforms

In a major international operation codenamed “PowerOFF,” Europol, collaborating with law enforcement agencies across...

Hackers Exploit Docker Remote API Servers To Inject Gafgyt Malware

Attackers are exploiting publicly exposed Docker Remote API servers to deploy Gafgyt malware by...