How to Recover a Discord Server After a Nuke
Discord does not restore deleted channels, roles, or bans. To recover a nuked server, stop the attacker, restore what was deleted, unban members, check member roles, and fix the permissions that made it possible. If Security Bot Recovery was on before the attack, it can put channels, roles, permissions, and member roles back. Without it, you rebuild by hand.
First ten minutes
Stop the attacker
As owner, strip the responsible account's roles or ban it. If a bot did it, kick the bot from Server Settings > Integrations.
Lock and pause
Run /lockall and pause invites under Server Settings > Invites (or Security Actions in the server menu) so nothing else happens while you work.
Command:
/lockallRead the audit log
Server Settings > Audit Log. Filter by the attacker. Note every deleted channel and role, every ban, and any webhooks or bots they created. Delete those webhooks and bots.
Do not start rebuilding while the attacker still has permissions or a bot they added is still in the server. The script will simply run again.
Restoring the structure
With Security Bot Recovery
Recovery is a Premium feature. It is off until you turn it on with the switch on the dashboard's Recovery page or with /recovery enable. Once it is on, it keeps two things:
- Backups. A copy of the server layout, taken automatically every 24 hours by default (every 6, 12, or 48 hours or once a week are the other options), plus any you take by hand.
- Recently deleted. Every role, channel, category, and emoji is saved the moment it is deleted, together with who deleted it, and kept for 90 days.
A backup holds:
- The server settings.
- Every role with its permissions, color, and position.
- Every category and channel of every type, with its permission overrides.
- Custom emojis.
- Which members had which roles (on servers with up to 50,000 members).
The newest 7 automatic backups are kept by default (you can keep 1 to 14), plus up to 10 manual ones.
When anti-nuke or Beast Mode punishes someone, Recovery keeps the newest backup from before the incident, so it is never rotated out. It also pauses automatic backups for two hours, so the damaged layout does not replace your good backups.
If Restore automatically after anti-nuke is on, it also puts back everything the punished account deleted in the last 30 minutes, without anyone pressing a button.
- Open the Recovery page. If the attacker only deleted things, select them under Recently deleted and restore them. Recreated roles get their channel overrides back in the channels that still exist, and members get those roles back from the newest backup that saved member roles.
- If the attacker also changed things, such as renaming channels, editing permissions, or creating spam channels, restore the last backup taken before the attack instead. Choose what to put back: missing roles and channels, Undo changes (changed roles, channels, permissions, and @everyone), the saved order, member roles, emojis, and server settings. Delete new channels and roles removes everything created after the backup, which clears spam channels in one go.
- Read the preview. It lists every step: what will be created, changed, deleted, and reordered, and how many members get each role back. Steps that touch roles above Security Bot's highest role are marked as blocked.
- Start the restore. It runs in the background in a fixed order: clean-up, roles, role order, categories, channels, channel order, emojis, server settings, member roles. It shows its progress and can be cancelled. By default it first takes a safety backup of the server as it is now, so the restore itself can be undone. If it stops partway, run it again. What it already recreated is not duplicated.
In Discord:
/recovery statusshows the current state./recovery backuptakes a backup now, and/recovery backupslists them./recovery restoreshows the plan for a backup with a confirm button./recovery viewlists recently deleted items./recovery role,/recovery text,/recovery voice,/recovery category, and/recovery emojirestore them by ID.
Restoring needs Administrator and a role above Security Bot's role, or server ownership. Security Bot itself needs Administrator.
What Recovery cannot do:
- Messages are not restored, because Discord does not allow it.
- Announcement, stage, and media channels can only be recreated while the server has Community enabled. A forum that cannot be recreated as a forum comes back as a text channel.
- Restoring server settings leaves the server description as it is.
- Recreated channels, roles, and emojis get new IDs, so bots and links that point at the old ones need updating.
- Deleted emojis are uploaded again on a best-effort basis.
- Roles above Security Bot's highest role cannot be changed or moved, so keep its role at the top.
- Channels in the categories you set as ignored (ticket categories, for example) are not saved.
- Bans are not part of a backup. Undo them from the audit log as described below.
Without Recovery
- Recreate categories first, then channels inside them, using the audit log for names.
- Recreate roles from the top of the hierarchy down, so permissions and colors are right before members get them.
- Recreate channel permission overrides for private channels. This is the slowest step. Use a staff channel to crowdsource what each channel allowed.
- Re-invite bots that were kicked and reconfigure them.
If you saved a Server Template before the attack, it holds categories, channels, roles, and permissions as of its last sync. It can only create a new server and skips forum and announcement channels, so use it as a reference or a limited fallback. Turn on Recovery before this happens again. Rebuilding a large server by hand can take days.
What Discord restores versus what Recovery covers
| Item | Discord | Security Bot Recovery (on before the attack) |
|---|---|---|
| Deleted channels and categories | Not restored | Recreated with their settings and permission overrides, from Recently deleted or a backup |
| Deleted roles | Not restored | Recreated with their permissions and color; a backup restore also puts them back in order |
| Members' role assignments | Not restored | Recreated roles go back to the members who had them in the backup and are still in the server |
| Renamed channels and roles, edited permissions | Not restored | Put back from a backup with Undo changes |
| Server name, icon, and verification level | Not restored | Put back from a backup with Server settings |
| Spam channels and roles the attacker created | Delete each one by hand | Removed by a backup restore with Delete new channels and roles |
| Deleted emojis | Not restored | Uploaded again, best effort |
| Bans issued by the attacker | Revoke each one in Server Settings > Bans | Not covered; find them in the audit log and unban separately |
| Deleted messages | Not restored | Not restored; Discord does not allow bots to |
| Who did it | Audit log, after the fact | Security log: anti-nuke warnings and the punishment. Recently deleted shows who deleted each item |
Recovery only has what it saved while it was on: backups taken before the attack and items deleted after it was turned on. Turn it on now on a Premium server, not after an attack.
Members and bans
Nuke scripts ban as fast as they can. Open Server Settings > Audit Log and filter by the attacker and the Ban Member action to get the list. Audit log entries are kept for 45 days. Then revoke each of those bans in Server Settings > Bans.
Unbanning does not bring people back by itself. Post an invite in your community's other channels (social media, a partner server) and ask people to rejoin.
Members who lost roles because the roles were deleted need them back. A Recovery restore does this for the members who had the role in the backup and are still in the server, as long as that backup saved member roles.
Members who rejoin after being unbanned, and anyone who joined after the backup, need theirs by hand. Reward and level roles can usually be recomputed by the bot that manages them. Staff and special roles need a list.
If the nuke came from a bot
A bot application that was given Manage Channels, Manage Roles, or Administrator behaves like a compromised admin, except that it keeps running until it is removed. Kick it from Server Settings > Integrations before anything else, then check the audit log for webhooks or roles it created and delete those too.
Going forward, keep Manage Server with the owner and one admin, since that is the permission that adds bots. Keep Security Bot's Anti Bot Add trigger on too. Whoever adds a bot is punished and the bot is kicked, unless they are the owner, ranked above Security Bot, or whitelisted.
Any bot ranked below Security Bot's role is subject to the same anti-nuke limits as a user. See what Discord raid bots are and how they work.
The first hour and the next day
| When | What to do |
|---|---|
| First 5 minutes | Strip the attacker's roles or ban the account, kick any unknown bot, run /lockall, pause invites. |
| First hour | Read the audit log, delete rogue webhooks, restore from Recently deleted or the last backup before the attack if Recovery was on, unban members from the attack window, check that staff have their roles back. |
| Next day | Rebuild anything Recovery did not have, re-invite kicked bots, require 2FA for moderator actions, review who holds Administrator, set anti-nuke limits, post a note to members. |
| First week | Watch the security log for repeat attempts, take a manual backup once the server is back to normal, have staff open a restore preview so they know the Recovery page, and write the incident down. |
Closing the hole
| Cause | Fix |
|---|---|
| Phished staff account | Require 2FA for moderator actions; staff change their passwords, which logs out every session |
| Malicious bot | Limit Manage Server to the owner and one admin; keep Anti Bot Add on |
| Over-permissioned role | Remove Administrator, Manage Roles, Manage Channels from everyone but the owner and one admin |
| No per-action limits | Set anti-nuke limits and punishments; put the bot's role at the top |
| Attack spread across accounts | Enable Beast Mode |
| Nothing saved the deleted channels | On Premium, turn Recovery on so backups and the Recently deleted list exist before the next incident |
| The restore waited for someone to come online | Turn on Restore automatically after anti-nuke on the Recovery page |
Common recovery mistakes
- Restoring before the attacker is out. The script runs again against the restored channels. Strip roles, kick bots, and delete webhooks first.
- Unlocking too early. Members flood back into half-restored channels and moderators lose the thread. Keep
/lockallin place until roles and overrides are back. - Restoring the wrong backup. A backup taken after the attack started already contains the damage. Pick the last one from before it. Recovery keeps that one automatically when anti-nuke punishes someone, and the preview shows exactly what would change.
- Deleting new channels and roles without reading the preview. The option also removes anything your staff created after the backup. Check the list of deletions first.
- Forgetting the bans. Recovery rebuilds the layout and member roles, not bans. Work through the attack window in Server Settings > Bans, with the audit log beside you.
- Rebuilding overrides from memory. Without Recovery, private channels end up visible to everyone. Confirm each override in a staff channel before unlocking.
- Fixing the symptom, not the cause. If a phished account did it and 2FA is still optional for moderators, it can happen again. The table above maps each cause to its fix.
- Recovery never turned on. Discovering during an incident that Recovery was off is the worst time. Turn it on now, check that the first backup appears on the Recovery page, and open a restore preview once so staff know where everything is.
Recovery settings by server type
| Server type | Recovery | Anti-nuke limits | Extra |
|---|---|---|---|
| Small community (under 1,000) | Optional; a manual rebuild may take an evening | Ban and kick limit 2, clear roles | 2FA for moderators; Administrator with the owner only |
| Public gaming server | Premium with Recovery on and daily backups (the default) | Ban limit 3, kick limit 3, clear roles | Beast Mode on; security log watched |
| Crypto, NFT, or marketplace | Premium with Recovery on, backups every 6 or 12 hours, and Restore automatically after anti-nuke | Ban limit 3, ban on channel and role delete | Web check with alt blocking; Beast Mode on; webhook trigger on |
| Server network | Premium on every server (3 servers $12.99, 7 servers $24.99 per month) | Per-server limits sized to each team | Someone in each time zone who can run the restore (Administrator ranked above Security Bot) |
Whatever the size, the aim is the same: fewer actions get through before the punishment fires, so there is less to restore. The setup guide covers the rest of the bot.
Report it
Nuking violates Discord's Terms of Service. Report the responsible account through Discord's report form with the audit log entries. Reporting does not restore anything, but it can get the account actioned so it cannot do the same to another server.
Write the incident down
Write a short note in your staff channel: who did what, when, how they got in, and what changed. It is the difference between this happening once and this happening again in six months, when the details are forgotten.
Do this with Security Bot
Discord Server Recovery Bot: Back up roles, channels, permissions, and emojis, keep what gets deleted, and restore the server after damage, abuse, or mistakes.
Security Bot backs up your server layout on a schedule and saves deleted roles, channels, categories, and emojis. After a nuke, a compromised account, or a mistake, check a preview and restore. It is part of Premium and off until you turn it on.
Frequently asked questions
Can Discord restore a nuked server?
No. Discord does not restore deleted channels, roles, or bans. Recovery depends on Security Bot's Recovery having been on before the attack, or on a Server Template you saved earlier.
How do I unban everyone after a nuke?
Filter the audit log by the attacker and the Ban Member action to list the bans from the attack, then revoke each one in Server Settings > Bans.
Does Security Bot restore deleted channels?
Yes, with Recovery on Premium, if it was on before the attack. Deleted roles, channels, categories, and emojis are kept under Recently deleted for 90 days, and automatic backups hold the whole server layout. You restore from the Recovery page of the dashboard or with /recovery.
Does Recovery give members their roles back?
Yes, for the roles it recreates: members who had the role in the backup and are still in the server get it back. That needs a backup that saved member roles: saving them is on by default and works on servers with up to 50,000 members.
Are messages restored?
No. Discord does not allow bots to restore deleted messages.
How do I stop it from happening again?
Require 2FA for moderator actions, keep Administrator with the owner, set anti-nuke limits with the bot's role at the top, enable Beast Mode, and turn on Recovery.
How do I know what Recovery saved?
Open the Recovery page: it lists your backups with what each one contains, and the recently deleted items with who deleted each. In Discord, /recovery backups lists the backups and /recovery view lists recently deleted items.
What if the nuke happened before I had Security Bot?
Nothing was saved, so follow the without-Recovery steps. Then invite the bot, move its role to the top, and on Premium turn Recovery on so the next incident is a restore instead of a rebuild.
How this guide was made: drafted with AI assistance, then checked against Security Bot's source code and Discord's official help articles. Spotted something out of date? Tell us in the support server.