-
Notifications
You must be signed in to change notification settings - Fork 0
Anti Nuke
Insider-threat protection - stop a rogue or hacked admin from nuking your server.
View this page in the localized AntiLink documentation
Anti-Nuke protects your server from the inside. Most protection stops strangers; Anti-Nuke stops a trusted admin who turns rogue (or whose account is hacked) from nuking the server: mass-deleting channels and roles, ban waves, mass webhook creation, or granting themselves dangerous permissions.
It works by watching admin actions and stepping in when someone who is not trusted does too much, too fast. The default response is a reversible quarantine (their roles are stripped so they cannot keep going), never an irreversible ban.
Warning
Anti-Nuke is a powerful feature that can remove roles from an admin. It is AntiLink Premium, off by default, and only the server owner, an Extra Owner, or the AntiLink team can change its settings - so a rogue admin cannot simply switch it off.
Each watched action has a limit (a count within a time window). When an untrusted admin crosses a limit - for example, 3 channel deletes in 20 seconds - Anti-Nuke applies your chosen action to them and logs it.
-
Quarantine (default) - strips every role the bot is able to remove and, if you set
one, adds a quarantine role. This is reversible: you restore their roles with one
click (or
/antinuke release). - Alert only - sends a warning to your alert channel without touching the admin.
The bot only ever removes roles it is allowed to (roles below its own highest role), and every action fails safe: if something cannot be done, Anti-Nuke downgrades to an alert rather than crashing or half-acting.
Anti-Nuke has a strict trust model. These are always immune:
- The server owner.
- The bot itself and other bots you did not flag.
- Extra Owners - co-owners you add, who also gain permission to configure Anti-Nuke.
- Trusted Admins - people you add who are immune but cannot change settings.
- The AntiLink team.
Everyone else with admin powers is watched. If Anti-Nuke ever cannot identify who did an action, it fails safe and does not punish anyone.
Turn Anti-Nuke on with /antinuke enable, or the dashboard Anti-Nuke tab.
Add every admin you fully trust as a Trusted Admin (/antinuke trust user:@Admin) so
normal administration is never flagged. Add any co-owners as Extra Owners
(/antinuke extraowner user:@CoOwner).
Set a quarantine role with /antinuke quarantinerole role:@Quarantine. Keep it below
the bot's highest role. Stripping roles already stops the damage; the quarantine role is
an optional extra restriction.
/antinuke logchannel channel:#mod-alerts so your team sees every trigger. Without one,
alerts go to the server's notification channel.
The defaults are conservative. Lower a limit to be stricter, raise it if your admins
legitimately make many changes at once. Configure everything in the dashboard or with
/antinuke.
- Anti-Bot-Add (on by default) - a bot added by an untrusted admin is removed. A classic nuke starts by adding a fresh bot. Turn on Ban rogue bots to ban instead of kick (needs the Ban Members permission).
- Panic Mode - automatically trips Emergency Lockdown when a nuke is caught, tightening the whole server while you respond.
| Action | Default limit |
|---|---|
| Channel deletes | 3 in 20s |
| Channel creates | 6 in 20s |
| Role deletes | 3 in 20s |
| Role creates | 6 in 20s |
| Bans | 5 in 20s |
| Kicks | 5 in 20s |
| Webhook creates | 4 in 20s |
| Permission escalation | 1 in 60s |
| Command | What it does |
|---|---|
/antinuke enable / disable
|
Turn Anti-Nuke on or off |
/antinuke status |
Show the current configuration |
/antinuke action mode: |
Quarantine (strip roles) or alert only |
/antinuke trust / untrust
|
Add or remove a Trusted Admin |
/antinuke extraowner / removeextraowner
|
Add or remove an Extra Owner |
/antinuke quarantinerole role: |
Role added to a quarantined admin |
/antinuke antibotadd enabled: |
Remove bots added by untrusted admins |
/antinuke banbot enabled: |
Ban (instead of kick) a rogue-added bot |
/antinuke panic enabled: |
Trip Emergency Lockdown on a nuke |
/antinuke logchannel channel: |
Where to post Anti-Nuke alerts |
/antinuke release id: |
Release a quarantine (restore roles) |
The dashboard Anti-Nuke tab does everything the command does, plus a quarantine log with a one-click Release button. Both write the same settings, so a change in either place applies within seconds.
They cover different threats and work well together:
-
Member Defense and Anti-Raid stop outsiders
- raids, join spikes and brand-new accounts arriving to cause trouble.
- Anti-Nuke stops insiders - a trusted admin (or a hacked admin account) abusing the powers they already have.
- AntiLink Premium on the server.
- The bot needs View Audit Log to attribute actions, and Manage Roles to quarantine.
- For Ban rogue bots it also needs Ban Members; the kick part of Anti-Bot-Add uses the same member intent as Member Defense.
Website | Dashboard | Documentation | Status | Support