Ransom DDoS Extortion Scam
Criminals send threatening emails claiming they will flood a business's servers with junk traffic (a DDoS attack) and take them offline unless a ransom is paid, usually in cryptocurrency.
Last reviewed: 11 June 2026
What this scam is
Ransom DDoS (RDDoS) extortion is a threat-based scheme in which attackers — or those merely claiming to be attackers — threaten to overwhelm a target's servers with a distributed denial-of-service attack unless a ransom is paid. A genuine DDoS attack floods a network with traffic from thousands of compromised machines, making websites, APIs, or other services unreachable to legitimate users. The ransom demand exploits the real cost and reputational damage such an attack can cause.
Many RDDoS campaigns are pure bluffs sent in bulk to businesses scraped from web registries and company directories. Others are sent by groups with genuine attack capability, though they often prefer the certainty of payment over the cost of running a large attack. The criminal business model relies on a percentage of recipients paying without verifying whether the threat is real.
How it works
Criminals identify targets — typically businesses with an online presence — by scraping domain registrar data, company websites, or professional directories for email addresses. Automated tools generate and send thousands of threat emails impersonating named attack groups.
Some campaigns include a brief, low-level 'teaser' attack lasting a few minutes to add credibility. This is relatively cheap to execute and significantly increases the payment rate. The teaser is not the scale of attack threatened — it is intended solely to demonstrate capability.
If payment is not received by the stated deadline, the criminal either moves on (pure-bluff campaigns) or may launch a modest attack before demanding a higher ransom. The second-demand pattern is common even after payment, making compliance a poor long-term strategy.
Why this scam works
Businesses that depend on online availability for revenue or customer trust — e-commerce stores, financial services, gaming platforms, SaaS providers — understand viscerally what even a few hours of downtime costs. The psychological threat of extended unavailability is extremely powerful even without a single packet of real attack traffic.
Many businesses also underestimate their own defences. Cloud hosting providers and CDN services typically include significant DDoS mitigation automatically, meaning the actual risk of a crippling attack is lower than it appears. The scammer profits from that underestimation.
A typical pattern
A business receives an email addressed to a technical contact or published abuse address. The message claims to be from a well-known DDoS-for-hire group and states that the business's online infrastructure has already been identified and tested with a small demonstration attack. The email demands a payment of several thousand dollars in Bitcoin within a specified window — often 24 to 48 hours — to avoid a sustained multi-day attack that would take the business offline, cost it customers, and damage its reputation. In many cases no demonstration attack ever took place. Businesses that pay often receive a second demand shortly afterward. Businesses that do not pay frequently find nothing happens at all, confirming the original threat was a bluff. In a minority of cases a real, low-volume attack is launched to add credibility.
Common red flags
- Unsolicited email threatening a DDoS attack if ransom is not paid
- Claim of a 'test attack' that you cannot verify in your own logs
- Demand for cryptocurrency only
- Impersonation of a named DDoS group to add credibility
- Very short payment window designed to prevent consultation with advisors
- Second demand arriving shortly after the first, or after payment
- Generic email with no specific technical details about your infrastructure
Sanitized example messages
Illustrative, sanitized examples. Personal details are replaced with placeholders such as [phone number] and [fake link].
"We are [GROUP NAME]. We will DDoS your network to 1Tbps starting [DATE] unless you pay [AMOUNT] Bitcoin to [WALLET]. We have already conducted a small test — check your logs."
"Pay [AMOUNT] within 24 hours or your site will be offline for days. We have taken down organisations much larger than yours. This is your only warning."
"You have ignored our first notice. The price has now increased to [HIGHER AMOUNT]. Pay now or the attack begins tonight and we will contact your customers to let them know why you are offline."
Common variations
- Named-group impersonation: email claims to be from a known DDoS collective to increase perceived credibility
- Escalating-demand variant: a low initial demand rises sharply if not paid within the window
- ISP-target variant: directed at smaller businesses whose hosting lacks built-in DDoS mitigation
- Gaming-server extortion: game server operators targeted during peak player periods when downtime costs are highest
- Combined ransomware-plus-DDoS threat: criminal claims to have both data and the ability to attack, doubling the pressure
How to verify before you act
Check server logs and your hosting provider's traffic dashboard at the time the claimed 'demonstration' attack took place. Real attack traffic leaves clear, measurable signatures. If logs show nothing unusual, the demonstration claim was fabricated.
Consult your hosting provider or CDN service before paying anything — they deal with these threats regularly, already have mitigation tools active, and will advise on whether the threat is credible. Law enforcement agencies have issued guidance confirming many RDDoS campaigns are bulk bluffs.
Payment methods used
- Cryptocurrency (Bitcoin, Monero)
- Bank/wire transfer
Who is usually targeted
- E-commerce businesses
- Online gaming platforms and game server operators
- Financial services and fintech companies
- SaaS and hosted service providers
- Any business with a publicly registered domain and technical contact email
What to do immediately
- Do not pay — payment does not guarantee the attack will not happen and will likely invite further demands
- Check your server and CDN logs to see whether any real attack traffic occurred
- Contact your hosting or CDN provider immediately — they have experience with these threats and active mitigations
- Report the email to your national cybercrime reporting body
- Preserve the full email including headers as evidence
- Brief relevant internal staff without creating panic — this is a known, common threat campaign
How to prevent it
- Use a CDN or DDoS-mitigation service that absorbs volumetric attacks at the network edge
- Ensure your hosting provider includes baseline DDoS protection in your service agreement
- Have an incident-response contact at your hosting provider established before any threat arrives
- Do not publish direct server IP addresses — route all traffic through protective services
- Create an internal communication plan so staff know not to panic or pay without proper escalation
- Report demands to law enforcement — agencies track these campaigns and sometimes identify the operators
Evidence to preserve
- Full email including all headers
- Wallet address or payment instructions in the email
- Server log exports covering the period the 'test attack' was claimed to have occurred
- Any follow-up communications
Where to report it
- Action Fraud (UK) — UK national fraud & cybercrime reporting centre
- FTC ReportFraud (US) — US Federal Trade Commission fraud reports
- FBI IC3 (US) — US Internet Crime Complaint Center
- Scamwatch (Australia) — Australian competition & consumer reporting
- Your bank's fraud line — Use the number on the back of your card or in your banking app — never a number the caller gives you
Always verify reporting routes and emergency contacts on the official government or agency website for your country.
Frequently asked questions
How do I know if the DDoS threat is real or a bluff?
Check your server logs and CDN dashboard for any anomalous traffic spikes at the time the 'demonstration' was claimed. If logs are clean, the demonstration was fabricated. Your hosting provider can also help assess whether your infrastructure is currently under any active pressure.
Should I pay to avoid the attack?
No. Security guidance universally advises against payment. Payment does not guarantee the attack will not occur, marks you as a target willing to pay, and frequently leads to repeated demands. Your CDN or DDoS-mitigation service is your best defence.
My site went down briefly after the email arrived. Does that mean the threat is real?
A brief low-level disruption is a known tactic some groups use to add credibility cheaply. It does not mean they can sustain the multi-gigabit attack they are threatening. Consult your hosting provider before concluding the worst.