Discord Server Nuke: Warning Signs and How to Protect Your Server

How nukes happen

A nuke needs permissions, not tricks. The common roots are:

• A staff account that was hacked or phished.
• A bot or app given Administrator that turned out to be malicious or got compromised, see bot token.
• A role with Manage Channels, Manage Roles or Ban Members handed to someone who should not have it.
• A leaked webhook or stolen invite to a bot with too many rights.

The common thread is that someone had destructive permissions they should not have had.

Prevention

1. Require two-factor authentication for moderators. Discord's server setting can enforce it for staff actions.
2. Grant Administrator to as few roles as possible, and none to bots unless needed.
3. Review authorized bots and webhooks regularly, and remove ones you do not use.
4. Keep an audit trail with server logs.
5. Turn on a bulk-action limit, described below.

Recovery

If it happens, remove the person or bot first, then reset permissions, then rebuild. Discord cannot restore deleted channels, so a server template and saved bot settings save a lot of time. Our nuke recovery checklist walks through each step in order.

How Noxyr's anti-nuke works

Anti-nuke reads the audit log to find who performed each destructive action: channel deletions, role deletions, bans and kicks. Actions are counted per person. If one actor passes max_actions inside window_seconds (defaults 3 and 30), the bot applies the chosen action to that person and posts to the log channel. The action can be timeout, kick, ban or none, where none only logs. It is off by default. The server owner is always exempt, and a trust list covers roles and users you want left alone. The bot needs View Audit Log and a role above the actor, as covered in role hierarchy.

Set it with /security antinuke or on the Security page. Read the anti-nuke docs, the anti-nuke guide and the anti-nuke bot page.

Staff habits that prevent it

Use unique passwords and two-factor login on every staff account, never click links from unknown direct messages, and remove permissions from people who leave the team. Most nukes start with one tired moderator clicking one bad link, so a small culture of caution matters as much as any setting.