How does a DDoS attack knock a website offline?
A DDoS (distributed denial of service) attack sends a site more traffic than its line or servers can handle, often from thousands of hijacked gadgets, so real visitors can't get in.

DDoS
A DDoS (distributed denial of service) attack tries to knock a website or online service offline. Often, nobody breaks in. Instead, hijacked gadgets send the site more traffic than it can handle. Its internet line, or the servers behind it, get overwhelmed, and real visitors can’t get in. The gadgets are usually part of a botnet: a hidden army of hijacked routers, cameras and TV boxes whose owners don’t know they’re involved.
Blocking source addresses works against smaller floods. But it barely helps against thousands or millions of sources. That’s why big sites use DDoS protection services. These filter the flood upstream, at an ISP (internet service provider), a CDN (content delivery network) or a mitigation provider, before it reaches the site’s own line.
What a DDoS attack actually sends
First, criminals build the botnet. Routers and cameras fall to factory-default passwords or unpatched security flaws. Some cheap TV streaming boxes even arrive with malware preinstalled, which the FBI described in its BADBOX 2.0 warning. Infection often goes unnoticed. On command, every bot fires at once.
The simplest attack fills the pipe: for example, 10 Gbps of junk aimed at a 1 Gbps line. Real packets get dropped too. A protocol attack jams the server instead. Each connection opens with a hello packet, a SYN. The server answers and keeps a half-open connection in the SYN-RECEIVED state until the final reply. In a SYN flood, that reply never comes, the backlog fills, and real visitors can’t get a seat. A third kind sends normal-looking web requests until the application itself chokes.
How DDoS protection works
- Small floods get blocked. When there are only a few sources, blocking their addresses can be enough.
- Big floods get filtered upstream. An ISP, CDN or mitigation provider drops the junk before it reaches the site’s line.
- Detection happens automatically. Cloudflare detected and mitigated the record attack below automatically.
- Servers can skip the seats. RFC 4987 describes SYN cookies, which allocate no state for connections in
SYN-RECEIVED, so a protected host can stay responsive during a SYN flood.
The result can be dramatic. In late 2025, the Aisuru-Kimwolf botnet, 1 to 4 million hosts made up mainly of Android TVs, peaked at 31.4 terabits per second in an attack lasting 35 seconds. That’s 31,400 Gbps, over thirty thousand one-gigabit lines. It’s the largest attack Cloudflare has reported, and Cloudflare stopped it automatically.
A DDoS is not a data breach
Many people think a DDoS steals data. By itself, it doesn’t. It targets availability: it knocks the service offline. But an attacker can use a DDoS as a smokescreen for a separate break-in while defenders are busy with the flood. So defenders watch for both.
What to do
- Check your Android TV box: open the Play Store, tap your profile icon, then Settings, then About, and look at Play Protect certification. If it says “Device is not certified”, or there’s no real Play Store, treat it as suspicious.
- Remember that one sign alone doesn’t prove a device is infected. For suspicious devices, the FBI says to consider disconnecting them from your network.
- Change factory-default passwords on your router and cameras.
- Install security updates so known flaws are patched.
Watch it in 60 seconds
