How to Stop Discord Raids: A Step-by-Step Protection Plan (2026)

To stop a Discord raid: raise your verification level, turn on automod flood and mention limits, add a honeypot channel that catches spam bots automatically, and keep anti-nuke enabled in case a staff account is compromised. If a raid is happening right now, jump to stopping a raid in progress.

What a Discord raid looks like

Most raids follow one of three patterns:

• Join raids: many new accounts join within seconds and post the same message or ping everyone.
• Self-bot spam: a handful of compromised or scripted accounts paste scam links into every channel they can see.
• Inside raids (nukes): a staff account or bot is compromised and starts banning members or deleting channels.

Each needs a different defence, so a good plan layers them.

Before a raid: prevention

1. Raise Discord's verification level

In Server Settings, set verification to at least Medium (account older than five minutes) or High (member for ten minutes before posting). Fresh accounts made for a raid then can't post immediately.

2. Limit who can ping @everyone

Remove the Mention @everyone permission from regular roles. Mass pings are the most disruptive part of most raids.

3. Turn on automod limits

With Krypton, enable flood and mention rules (automod enable flood mentions) and set a timeout action (automod action flood timeout 1h). Krypton Premium also detects raids where new members post the same message at once and flags very new accounts posting links or invites. See Krypton AutoMod.

4. Add a honeypot channel

Create a channel that tells members not to type in it. Spam scripts post everywhere, so they post there too. Krypton's Honeypot softbans any account that does, deleting its last hour of messages across the whole server. Read the honeypot setup guide.

5. Protect against inside raids

Enable Anti-Nuke (antinuke enable) so a compromised admin or bot is punished the moment it starts mass-banning or deleting channels, and set up a backup code so someone can still manage security if the owner account is lost.

During a raid: stop it fast

1. Pause invites. In Server Settings > Invites, pause invites so no more accounts can join.
2. Raise verification to the highest level temporarily.
3. Lock busy channels so only staff can send messages until it is over.
4. Let automation work: automod timeouts and honeypot softbans remove accounts faster than any moderator.
5. Don't click anything raiders post, and tell members the same.

After a raid: clean up

• Remove leftover spam: honeypot softbans already delete each raider's last hour of messages; purge anything left.
• Review the logs: Krypton's automod cases and server logs show who joined and what they did.
• Check staff accounts: if a staff member's account posted spam, reset their roles until they secure it.
• Re-open gradually: resume invites and lower verification once things are calm.

The short checklist

• Verification level Medium or High.
• @everyone mentions restricted.
• Krypton AutoMod flood and mention rules on.
• Honeypot channel set up.
• Anti-Nuke enabled and backup code issued.