VaultCord is the anti-nuke pick for getting your server back. It restores channels, roles and settings from backups kept for life, rebuilds channels and roles even without a backup, and auto-pulls members into a replacement server if yours is deleted. Pair it with a limit-based bot like Wick if you want rogue admins stopped mid-action.
Anti-nuke bots side by side
| VaultCord | Wick | Security Bot | |
|---|---|---|---|
| Stops actions as they happen | No | Yes | Yes |
| Restore from backup | Every plan, kept for life | Premium | “Automatic Server Recovery” on Premium |
| Recovery without a backup | Yes | Not in its docs | Not described |
| Members into a new server | Unlimited, 1 every 0.98s | Not in its docs | Not in its feature list |
| Auto-pull if the server is deleted | Yes | Not in its docs | Not in its feature list |
| Deletion alerts by email | Premium and Plus | Not in its docs | Not in its feature list |
| Scheduled backups | Plus | Not in its docs | Not in its feature list |
| Starting price | Free | Free, Premium per server | Free, $3.49/mo |
Sources: Wick docs, Security Bot premium, Security Bot docs.
What a nuke is, and why limits are not enough
A nuke is when someone with high permissions deletes channels and roles, bans members in bulk, or deletes the server. It is usually a staff account that got phished, a moderator with a grudge, or a bot that was given Administrator and then compromised.
Limit-based bots such as Wick and Security Bot count dangerous actions and stop whoever goes over. They are good at it. They cannot act on the owner account or on anyone ranked above their own role, and a careful attacker can stay under a threshold. So every server needs a plan for the nuke that gets through.
Before a nuke
- Keep Administrator on as few roles as you can.
- Turn on 2FA for moderator actions in your server’s Safety Setup.
- Remove bots you no longer use.
- Take a VaultCord backup now, and before any big change. On Plus, schedule them.
- Have members verify through your VaultCord bot so you can pull them later.
After a nuke, with VaultCord
- Remove the account or bot that did it, and reset the passwords and tokens involved.
- If the server still exists, restore from your latest backup. Channels, categories, roles, permissions and server settings. Paid plans add messages, emojis, stickers, bans and member role assignments.
- No backup? Use instant recovery: instant server recovery for channels and roles even without a saved backup (Denukify-style).
- If the server was deleted, VaultCord auto-pulls your verified members into a replacement server. You can also pull by hand from the dashboard or the app.
- Watch the pull in the realtime migration logs. At one member every 0.98 seconds, on every plan, 1,000 members take about 16 minutes.
Mistakes that make a nuke worse
- No recent backup. A backup from six months ago brings back six-month-old channels. Take one before every big change.
- Restoring with the attacker still inside. Remove the account or bot first, or the rebuild gets deleted again.
- Members who never verified. Only members who authorized your bot can be pulled. Post the verify message early, not after an incident.
- Two bots fighting. If you run an anti-nuke bot, whitelist VaultCord so a restore is not treated as an attack.
The setup we would run
One live-limit bot at the top of the role list, and VaultCord for the verify gate, backups and member restore. That covers the moment of the attack and the hour after it. Compare the two halves directly in VaultCord vs Wick.