How it typically works?
- Identify reflectors: attackers scan for services that respond with large payloads to small requests.
- Spoof source: requests are crafted with the victim IP as the source so replies go to the victim.
- Trigger responses: reflectors return larger responses that are directed at the victim.
- Aggregate amplification: many reflectors amplify traffic into a concentrated flood at the target.
Common techniques & variants
- DNS amplification: use open DNS resolvers to return large answers to small queries.
- NTP amplification: abuse network time protocol monlist or similar features to return large responses.
- Memcached amplification: exploit memcached servers to return megabyte scale responses per request.
- SSDP and CHARGEN abuse: older UDP based services still present on some networks can be used as reflectors.
- Multi protocol reflection: combine multiple reflector types to aggregate amplified traffic.
Impact
Amplification attacks are effective at generating very large traffic volumes that overwhelm links and scrubbing capacity. They are particularly dangerous because they can be launched by attackers with minimal bandwidth. SecOps teams must detect reflected traffic patterns, work with providers to block or null route attacking flows, and harden infrastructure to reduce available reflectors. Disabling or rate limiting vulnerable services and ensuring source address validation at network edges reduces the pool of potential reflectors.
Further reading
- Cloudflare: Amplification attacks explained. Read more
- Arbor Networks: Reflection and amplification threat analysis. Read more
- CERT: Guidance on reflector based attacks. Read more
- CISA: DDoS and amplification advisories. Read more