Quick answer
A smurf attack is a DDoS attack that sends ICMP echo requests with a forged source address to a network's broadcast address, so every host there replies to the victim and floods it. Modern routers block it by default.
Formula: amplification factor = number of hosts that answer the broadcast
What is a smurf attack?
A smurf attack is a distributed denial-of-service (DDoS) attack that floods a victim with ICMP echo replies (the "ping" response). The attacker sends ICMP echo requests to a network's broadcast address and forges the source address so it looks like the victim's. Every host on that network that answers the broadcast sends its reply to the victim, who is flooded with traffic it never asked for.
Two features make it work: IP directed broadcast (one packet sent to a network's broadcast address is delivered to every host on that network) and source address spoofing (the attacker can claim any return address). The network that unknowingly multiplies the attack is called an amplifier. The attack was described in a CERT advisory in January 1998, and today it is mostly a teaching example: routers stopped forwarding directed broadcasts by default in the late 1990s, as the next sections show.
How a smurf attack works, step by step
- Find an amplifier. The attacker finds a network whose router forwards directed broadcasts and whose hosts answer broadcast pings.
- Spoof the source. The attacker crafts ICMP echo requests with the victim's IP address as the source address.
- Send to the broadcast address. The packets are sent to the amplifier network's broadcast address, for example the last address of the subnet.
- The network multiplies it. Each live host replies with an echo reply, addressed to the victim.
- The victim is flooded. Replies from every host on every amplifier network arrive at once. The victim's link saturates, and legitimate traffic cannot get through.
A close relative is the fraggle attack, which does the same with UDP echo packets instead of ICMP.
The amplification arithmetic
Sample data: a standard ping packet is 84 bytes on the wire (20-byte IP header + 8-byte ICMP header + 56 bytes of data), which is 84 × 8 = 672 bits. The attacker sends 1,000 spoofed requests per second, and the victim has a 100 Mbit/s link.
| Quantity | Value | Calculation |
|---|---|---|
| Attacker's outgoing traffic | 0.672 Mbit/s | 1,000 packets/s × 672 bits |
| Hosts answering on amplifier network A | 250 | |
| Replies reaching the victim from A | 250,000 packets/s | 1,000 × 250 |
| Traffic from A at the victim | 168 Mbit/s | 250,000 × 672 bits |
| Amplification factor | 250× | 168 ÷ 0.672 |
| Three amplifier networks (250 + 100 + 50 hosts) | 268.8 Mbit/s | 1,000 × 400 × 672 bits |
The amplification factor equals the number of hosts that answer. A single amplifier network of 250 hosts already exceeds the victim's 100 Mbit/s link (168 > 100); three networks send 2.7 times the link's capacity. The attacker needs well under 1 Mbit/s of bandwidth, which is why the technique was attractive. It is also why the traffic cannot be traced back to the attacker easily: the packets the victim sees come from innocent hosts.
Why smurf attacks are now rare
Three defences, each cheap, closed the hole:
- Routers do not forward directed broadcasts by default. RFC 2644 (August 1999, BCP 34) says routers must default to blocking receipt and forwarding of network-prefix-directed broadcasts, and names Smurf as the reason.
- Ingress filtering. BCP 38 (RFC 2827) asks networks to drop outgoing packets whose source address does not belong to them, so spoofed packets are stopped at the attacker's own provider.
- Hosts ignore broadcast echo requests. Operating systems and devices can be configured not to reply to ICMP echo sent to a broadcast address.
The same idea survives in a different form. Modern reflection and amplification attacks also spoof the victim's address, but they use public servers (DNS, NTP and similar UDP services) instead of broadcast pings. If you operate a network, the defences above still apply: block spoofed sources leaving your network, and disable directed broadcast.
A checklist for network operators
- Confirm that every router interface has directed-broadcast forwarding disabled, and keep it that way after firmware upgrades.
- Apply ingress and egress filtering so packets leaving your network carry only your own source addresses.
- Configure hosts and printers not to answer ICMP echo sent to a broadcast address.
- Ask your upstream provider whether they can drop attack traffic close to the source, since your own link is already full by the time you notice.
- Keep a record of normal ICMP volume, so a sudden jump is obvious when it happens.
Smurf attack versus other floods
| Attack | How the flood is produced | Needs a botnet? | Needs spoofing? |
|---|---|---|---|
| Smurf | Broadcast pings answered by many hosts | No: the amplifier is the multiplier | Yes |
| Fraggle | Same, with UDP echo | No | Yes |
| Reflection (DNS and similar) | Small queries to public servers that send large replies | No, but often used with one | Yes |
| Volumetric flood from a botnet | Many compromised devices send traffic directly | Yes | Not required |
The difference from botnet floods matters for defence: with a smurf attack there is no army of infected devices to clean up; the fix sits in network configuration.
Common misunderstandings
- "Smurf is malware." It is a technique, not a program you can catch. Some sources link the name to an early attack tool; the effect is on the network, not on a device you own.
- "A firewall on my server stops it." The flood saturates your link before it reaches your server. Mitigation happens upstream, at your provider or a scrubbing service.
- "It is the same as a ping flood." A ping flood is sent directly by the attacker. A smurf attack gets other hosts to do the sending.
- "Rate limiting at the application fixes it." Rate limiting and bot mitigation work on requests that reach your application. A network-layer flood never gets that far.
- "It is a current threat to most websites." Misconfigured networks still exist, but it is far less common than HTTP floods or reflection attacks.
What a smurf attack looks like in website analytics
TapCub is not a security or network product and does not detect or stop smurf attacks. A smurf attack is made of ICMP packets that never run a web page, so no pageview or script event is created. What you can see is the effect: your site stops answering, and the visitors you normally get disappear.
- Watch for the drop. In Web analytics › Realtime, an outage shows as live visitors falling toward zero while nothing changed on your side. Compare it with the same hour on earlier days in Web analytics › Overview.
- Alert on a sudden fall. A monitor in All-platform analytics › Operations › Monitors can check pageviews or visitors per hour or day and notify you when the value crosses your threshold. It only notifies.
- Check crawl health. If you send server data or import logs, Monitoring › Crawl health shows search-engine fetches with their 5xx counts, which is a way to see an outage from the crawler's side. With only the page script, you do not see crawlers that do not run JavaScript.
- Annotate the incident. Add a date annotation in Configuration › Annotations so the dip is not mistaken for a marketing failure later.
- Fix it elsewhere. Mitigation is a network task for your host, provider or a DDoS protection service. TapCub only records that traffic fell.
Not legal or security advice.
Sources
- IETF, RFC 2644: Changing the Default for Directed Broadcasts in Routers (BCP 34), August 1999.
- IETF, RFC 2827: Network Ingress Filtering (BCP 38), May 2000.
- Cloudflare Learning Center, Smurf DDoS attack.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Analyst
Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.