Skip to main content
Antinuke watches the audit log. When someone performs too many destructive actions inside a time window, they get punished and — where possible — the damage gets reverted. It’s aimed squarely at the threat other systems can’t touch: people who already have permissions. A compromised admin account, a staff member who’s decided to burn the place down, a bot with more scope than it should have.

​
Who can configure it

Antinuke is deliberately locked tighter than everything else. Only the server owner and members explicitly added as managers can change its settings — Administrator alone isn’t enough, because an attacker who gains Administrator would otherwise just turn it off.
Aliases for trust: manager, mod, admin.

​
Who gets alerts

Aliases for alerts: alert, notify, recipients. Recipients can also be picked from Alerts in the panel.

​
The control panel

Opens a panel showing every protection and whether it’s on. Pick one from the menu to toggle it and set its threshold and time window. Punishment & Access is where you choose the punishment and pick whitelisted members. Only the server owner can change trusted managers from the panel.

​
Modules

Each module is toggled independently and has its own threshold and window.
Read a threshold as “more than N of this, within this window, gets you punished.”

​
Modules with no threshold

Any bot added to the server is immediately kicked, and whoever added it is punished. There’s no threshold — one is enough.This is the single highest-value toggle in the whole system. Adding a malicious bot is by far the most common way a server actually gets nuked, because it takes one click and needs no permissions of the attacker’s own beyond Manage Server.Legitimate additions still work — whitelist yourself, then add the bot.
Watches for dangerous permissions being granted to a role — Administrator, Ban Members, Manage Roles, Manage Guild and similar. When one appears, the grant is instantly reverted and whoever made it is punished.This catches the subtler attack: rather than deleting anything, the attacker quietly gives @everyone Administrator and comes back later. Aliases: permission, perms.
Detects mass-mention spam being pushed through a webhook, deletes the messages and removes the webhook. Webhooks bypass most other protections because they aren’t a member, which is exactly why this exists separately.Aliases: wspam, hookspam, whspam, mentionspam, spam.

​
Punishment

stripstaff is worth considering for a large staff team — it neutralises the account without the drama of a ban, and !stripstaff restore @them puts every role back once you’ve worked out what happened. jail needs the jail role set up first, via !setup. Aliases for the command: action.

​
Whitelisting

Two different lists, for two different things:
Aliases for whitelist: exempt, wl. Be careful with who is whitelisted. The whole point is that a compromised admin account isn’t trusted. Bots that legitimately mass-manage things — a ticket bot creating channels, a role bot doing bulk assignment — do need whitelisting or they’ll trip thresholds during normal operation.

​
Restoring after an attack

When a module fires and something can be put back, the alert tells everyone who receives it to run antinuke restore in the server. The restore message lists every role, channel and ban the perpetrator touched, including what they did before the threshold tripped, and lets you restore everything at once, one kind at a time, or pick individual items. It stays available for 2 days.
Aliases: revert, undo, restoration, revision. The owner and trusted managers can run it. Restoring:
  • Recreates deleted roles with their name, color, position and permissions, and re-assigns them to everyone who had them
  • Recreates deleted channels in their category, with their topic, settings and permission overwrites
  • Reverts renamed or edited roles and channels to how they were
  • Deletes roles and channels the perpetrator created
  • Unbans the members they banned
Snapshots are kept for 48 hours. After that you’re back to backups.

​
Reviewing the configuration

Everything is in the panel: every module with its threshold and window, the punishment, the whitelist, the managers and the alert recipients. antinuke settings and antinuke config open the same panel.

​
Command reference

Group aliases: antiwizz, an, aw.