The best Discord anti-raid bot stops raiders before they can post. VaultCord does that at the verify gate: new members pass a captcha and an account age check, and on paid plans alt, VPN, IP, country and ASN blocks, before they get a role. Wick and Security Bot react to join spikes after raiders arrive.
Anti-raid bots side by side
| VaultCord | Wick | Security Bot | Double Counter | |
|---|---|---|---|---|
| How it stops raids | Verify gate before any role | Anti-raid and lockdown (Premium) | Join scoring, then punish and lock | Alt and VPN checks at verification |
| Captcha | Every plan | Yes | Yes | Yes |
| Minimum account age | Every plan | Not compared | Not compared | Not in its feature list |
| Alt detection | Premium and Plus | Not compared | Scoring flags alts | Free |
| VPN, IP, country, ASN blocks | Premium and Plus | Not compared | Not compared | VPN protection |
| Rebuild after a raid | Backups, member restore | Backups on Premium | Not described | Not in its feature list |
| Starting price | Free | Free, Premium per server | Free, $3.49/mo | Free, Pro via Discord |
“Not compared” means we did not find that check described in the bot’s own docs. Sources: Wick docs, Security Bot, Double Counter Pro.
What a raid looks like
A raid is a wave of accounts joining at once to flood channels with spam, slurs, scam links or pings. Most are fresh accounts, alts or bots run through VPNs. The damage happens in the first minute, which is why a bot that reacts after the joins is always racing. A gate that holds every new account until it passes checks takes that race away.
Set up a verify gate with VaultCord
- Create your branded bot from the VaultCord dashboard and add it to your server.
- Make a verified role. Set your channels so @everyone cannot see them and the verified role can.
- Leave one verify channel visible to everyone and post the verify message there with
/verify-embed. - Move the bot’s role above the verified role so it can hand it out.
- Turn on captcha and a minimum account age. On Premium, add alt detection and VPN, proxy and cellular blocking.
- Watch the rejected member review queue for real people who got caught, and accept them by hand.
Settings that keep real people in
A gate that is too strict blocks your own community. Start with these and tighten during a raid:
- A minimum account age of a few days catches most fresh raid accounts. Raise it to weeks only while a raid is on.
- Cellular blocking can catch real members on mobile data. Leave it off unless raiders are coming through phone networks.
- Country and ASN blocks are precise tools. Use them when your logs show a raid coming from one network, not as a default.
- Check the review queue daily. Accepting a real person by hand takes one click and keeps them from leaving.
Discord’s own tools
Use them alongside a bot. Discord’s Security Actions let moderators pause invites and pause DMs between members who are not friends, with a banner showing when the pause ends. Raid Protection alerts sit under Server Settings, Safety Setup, and Discord says they are rolling out gradually. Your server verification level adds one more floor.
During a raid
- Pause invites from Security Actions.
- Turn on slowmode in the channels being hit.
- On VaultCord, raise the minimum account age and turn on VPN blocking until it is over.
- Ban the wave from the member list, sorted by join date.
- Check the verification logs for the IPs, countries or ASNs they came from and add them to the blocklist.
If a raid turns into a nuke, follow the anti-nuke recovery steps.