search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Short, Sharp, Catastrophic


Gcore breaks down the 6 Tbps AISURU DDoS targeting hosting providers


Andrey Slastenov, Head of Security at Gcore, explains how the 6 Tbps AISURU DDoS attack unfolded and what it reveals about rising short-burst assaults and global infrastructure weaknesses.


One of the largest DDoS attacks ever recorded has been blocked by Gcore, after a short-burst, high-intensity assault targeting a hosting provider serving the gaming sector peaked at 6 Tbps and 5.3 Bpps.


Although the attack lasted less than 45 seconds, its methodology and scale matched recent AISURU botnet activity, underlining how rapidly modern botnets can overwhelm critical infrastructure.


More than half of the malicious traffic originated from Brazil and nearly a quarter from the US, reflecting how unsecured, high- density device regions continue to fuel large-scale botnet operations. Gcore’s globally distributed network and AI-driven DDoS Protection were able to mitigate the incident without service disruption—an outcome that reinforces the growing need for integrated, real-time defence as attacks evolve in volume and complexity.


Te incident echoes findings from Gcore’s latest Radar Report, which warns that the gaming sector remains one of the most targeted industries and has seen a 41 per cent rise in DDoS activity in recent months. With attack patterns shifting toward short, powerful bursts and multi-regional origins, the case highlights why gaming companies and their hosting providers must strengthen resilience with sophisticated, AI-enabled cybersecurity.


Speaking to G3, Andrey Slastenov, Head of Security at Gcore, outlines how the company mitigated a 6 Tbps DDoS in real time and why attackers are shifting to rapid-burst, application-layer tactics.


88


Andrey, what made the recent DDoS attack one of the largest ever recorded, and what indicators confirmed its association with the AISURU botnet?


We were able to confirm its association with the AISURU botnet because the methodology and short-burst volumetric flooding that characterised this attack are consistent with the behaviour and scale of recent AISURU-attributed incidents. It is one of the largest attacks recorded due to its peak volume of 6 Tbps and peak packet rate of 5.3 Bpps.


Te attack lasted only 30 to 45 seconds but reached 6 Tbps. Why are these short-burst, high-intensity attacks becoming more common, and what makes them so difficult to defend against?


Short-burst, high-intensity attacks have historically been the standard employed by DDoS threat actors. In Q1-Q2 2025, they made up 57 per cent of global attacks. However, this is the first time we are seeing an attack of such unprecedented magnitude – 6 Tbps. Te unpredictable, irregular traffic patterns of such attacks closely mimic legitimate user behaviour, complicating real-time detection and mitigation efforts. Attackers can use large bursts to quickly overwhelm infrastructure before traditional defences activate, thus causing massive disruption in seconds.


Tese short-burst attacks are also a preferred tactic because they allow attackers to probe resilience without committing to long campaigns, enabling them to analyse and understand defence


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134