Skip to content
Guide

How to protect a Discord server from nukes

A Discord server gets nuked when an account or bot with powerful permissions mass-deletes channels and roles, bans members or spams everyone. To protect yours, keep Administrator and other takeover permissions on as few roles as possible, require 2FA for moderators, order your roles carefully, vet every bot, back up your structure, and get alerted the moment something goes wrong.

By Digital DenUpdated November 5, 20266 min read

How servers get nuked

A nuke is not a hack of Discord itself. Someone uses permissions the server already gave out. It usually comes from one of three places:

  • A staff account taken over through a phishing link, a fake login page or a leaked password.
  • A bot that is malicious, abandoned or compromised, holding Administrator or other powerful permissions.
  • A staff member who turns on the server, or was trusted with more than they needed.

Every one of these is limited by what the account can do. That is why prevention is mostly about permissions.

1. Limit Administrator and takeover permissions

Every nuke needs permissions. Administrator grants all of them, and Manage Roles, Manage Channels, Manage Webhooks, Ban Members and Kick Members each hand over part of the server. The fewer people and bots that hold them, the fewer accounts an attacker can use. What each permission can do.

  • Keep Administrator to two roles or fewer, held only by people you trust completely.
  • Give moderators the specific permissions they use, not Administrator.
  • Keep every one of these off @everyone, and off roles that onboarding or reaction roles hand out.

2. Require 2FA for moderator actions

Most nukes start with a stolen staff account. With Server SettingsSafety Setup set to require 2FA for moderator actions, a stolen password alone cannot ban, kick or delete. Only the server owner can turn it on, and the owner needs 2FA first.

  • Turn on Require 2FA for moderator actions.
  • Ask every staff member to enable 2FA on their account.

3. Use the role hierarchy

Discord only lets someone manage roles and members below their own highest role. Order the list in Server SettingsRoles so it matches who you trust, and a compromised moderator cannot touch the roles or people above them.

  • Put your most trusted roles at the top, then staff, then members.
  • Keep bot roles only as high as each bot needs to manage the roles below it.

4. Vet every bot

A bot with powerful permissions is a staff account that never logs out. If it is abandoned, compromised or malicious, it can do anything its role allows.

  • Add bots only from developers you trust, and untick permissions they do not need on the invite screen.
  • Never give a bot Administrator just because its invite asks for it.
  • Remove bots you no longer use, in Server Settings > Integrations.

5. Back up your structure

A Discord server template records your channels, roles and permission settings. Create one in Server SettingsServer Template and sync it after big changes. It cannot be applied back onto your server, and it holds no messages or members, but it is an exact blueprint of the layout to rebuild from.

  • Create a template, sync it after big changes, and keep its link with the owner.

6. Know the moment it starts

A nuke takes minutes, so how fast your team hears about it matters. EvaluBot's permission alerts tell a staff channel and the server owner when:

  • 5 or more channels, roles, emoji, stickers or sounds are deleted within a minute, or 10 or more channels or roles are created
  • 5 or more members are banned, kicked or pruned within a minute
  • One account does damage, fast or slow, or someone does damage soon after being given power
  • A security or moderation bot is removed
  • Any role gets Administrator, including a newly added bot's role, or a member is given one
  • The server's ownership is transferred, or Discord detects a raid or DM spam
  • 2FA for moderator actions is turned off, on Premium

Each alert names who did it, and bulk and one-account alerts name any protection switched off just before. Every one of these is a critical alert, free on every server, except the 2FA alert. EvaluBot's alerts only alert: they never revert or block a change. An EvaluBot audit also scores your server against the weak spots above, so you can fix them before anyone tries.

Anti-nuke bots and the trade-off

Bots that undo or punish changes automatically need permissions like Ban Members and Manage Roles, and often Administrator, to do it. That can be worth it, but it makes them one more powerful account to trust. Whichever you choose, the steps above shrink what any single account can do.

If it happens

  1. 1Remove the responsible account's roles, or kick the bot. The server owner can always do this.
  2. 2Open the audit log to see exactly what was changed, deleted and banned, and by whom.
  3. 3If a staff account was taken over, its owner should change their password and turn on two-factor authentication before getting their roles back.
  4. 4Recreate deleted channels and roles using your server template as the blueprint, then unban members who were caught up in it.

How to read the audit log.

FAQ

What does it mean to nuke a Discord server?

Using powerful permissions to wreck a server in minutes: mass-deleting channels and roles, banning members, or pinging everyone with spam. It is usually done from a compromised staff account, a rogue staff member, or a malicious or compromised bot.

How do I stop my Discord server from being nuked?

Keep Administrator and other takeover permissions on as few roles as possible, require 2FA for moderator actions, keep staff and bot roles in the right order, give bots only the permissions they need, back up your structure with a server template, and set up alerts for mass deletions and new admins.

Is EvaluBot an anti-nuke bot?

No. EvaluBot's audits and alerts never change, revert or block anything. It audits your server for the weak spots a nuke relies on, and its permission alerts tell your staff right away when channels or roles are deleted or created in bulk, members are removed in bulk, one account starts doing damage, a security bot is removed or someone is handed Administrator.

Can a server template restore a nuked server?

Not in place. A Discord server template creates a new server with the same channels, roles and permission settings, without messages or members. Use it as the blueprint for rebuilding what was deleted, or to start fresh if the damage is severe.

Find the weak spots before anyone else does.

One read-only /audit scores your server against the permissions a nuke relies on, and alerts tell your staff the moment something goes wrong.

Join the Discord servers already running EvaluBot.

Running a busy server? Premium gives it 15 audits a month, every risky change as an alert, fix plans and more. See Premium