Ransom DDoS (RDDoS)
A ransom DDoS (RDDoS) is extortion: attackers threaten or launch a DDoS attack unless you pay. How to respond without paying, and how to prepare.
What is a ransom DDoS attack?
A ransom DDoS (RDDoS) attack is extortion with a DDoS attack as the threat. Criminals send a note that demands payment and warns that your site or network will be flooded with traffic if you refuse. Some start with a short demonstration attack to be taken seriously; many never attack at all and only hope you pay. Either way, the right response is preparation and reporting, not payment.
How it unfolds
- The note. It arrives by email, a contact form or a support ticket, often addressed to a generic role. It names a sum, a payment method (typically cryptocurrency) and a deadline.
- Optional demonstration. A brief flood can make the threat look credible. Its absence does not mean the threat is empty.
- The attack, if it comes. Traffic is aimed at network layers 3 or 4, or at the application layer, using a botnet or a rented DDoS service. Compare a DDoS attack, an application layer attack and an HTTP flood.
- Follow-up. Attackers may demand more money later, so paying does not buy lasting peace.
What to do when you receive a ransom note
- Do not pay. Payment does not guarantee the attack never comes or stops, and it marks you as a target worth demanding more from.
- Keep the evidence. Save the message with its headers, the sender details and any payment address, and note the time.
- Report it. Tell your national cybercrime or CERT contact, such as the FBI's IC3 or CISA in the US, and inform your hosting, CDN or DDoS protection provider.
- Check your protection now. Confirm that every internet-facing asset, including the origin, DNS servers and secondary IP ranges, sits behind mitigation. Attackers go for the unprotected address.
- Brief your team. Make sure the people who handle support and contact mailboxes know to forward such notes to security instead of replying.
How to prepare
The preparation is the same as for any DDoS attack: put a mitigation service or CDN in front of the origin, keep origin addresses private, rate-limit expensive endpoints, tune alert thresholds to your normal traffic and write a response plan with named owners. The UK NCSC reduces this to four habits: understand your service, understand your defences, create a response plan and test your response. See how to stop DDoS attacks, DoS protection and cyber security threats.
Where load testing and monitoring fit
LoadFocus does not simulate DDoS or ransom DDoS attacks and cannot protect you from one. What it does is show your capacity limit under normal traffic, so you know how much headroom you have: run a cloud load test and read spike testing to plan scenarios. API monitoring alerts you when an endpoint slows down or fails (every 5 minutes on the free plan), which can be the first outside sign that something is wrong. Only test systems you own or have written permission to test, and never test a third party's service.
FAQ: ransom DDoS
Should I pay the ransom?
No. Payment does not guarantee the attack will not happen, and attackers can come back with a larger demand. Report the message and check your protection instead.
Is a ransom DDoS threat always real?
Not always, but you cannot tell from the note. Treat it as possible: verify your DDoS mitigation covers every exposed address and that your response plan works.
How is it different from ransomware?
Ransomware encrypts your data and demands payment to unlock it. A ransom DDoS leaves your data alone and threatens to take your service offline.
Can load testing stop or simulate a ransom DDoS?
No. Load testing neither defends against attacks nor replaces authorised attack simulation, which only your protection provider can run under agreed rules. A load test shows how much normal traffic your system handles before it slows down.
Related LoadFocus Tools
Put this concept into practice with LoadFocus, the same platform that powers everything you just read about.