Anti-Nuke
Stop a rogue or compromised admin from nuking your server with mass bans, mass deletions and dangerous permission grants.
Anti-nuke watches the audit log for destructive admin actions (mass bans, mass kicks, channel or role deletions, rogue webhooks and bot adds) and punishes whoever crosses a threshold, even if they are an admin. It is your protection against a compromised or rogue admin account, and it is off by default.
Commands
,antinuke (alias ,an) needs Administrator:
,antinuke ban on --threshold 3 --do ban punish mass bans past a threshold
,antinuke whitelist add @bot exempt a trusted user or bot
,antinuke admin add @user let someone configure anti-nuke
,antinuke list list modules and their state
,antinuke config show the full configuration
The full module set (mass kick, mass prune, channel and role create/delete, dangerous permission grants, webhook create, bot add, server update) is toggled on the dashboard's Antinuke page. A new, unwhitelisted bot being added is blocked automatically.
Example
Auto-ban anyone who mass-bans, and whitelist your logging bot:
,antinuke ban on --threshold 3 --do ban
,antinuke whitelist add @AuditBot
,antinuke admin add @Owner
Related
- For a one-off scan of risky roles and permissions, run
,secaudit(aliases,securityaudit,,permaudit). - To stop a single rogue moderator using bot commands, see Moderator Accountability.
- To strip a dangerous member's powerful roles by hand, use
,stripstaff.