Security

Antinuke

Set restrictions on your staff to prevent harm from being done on your server.


Note:

Slash commands for this page

Set this up in Discord with /configure feature:Anti-nuke, or on the dashboard under Security › Antinuke.

Use the slash version of each command below. Prefix commands keep working until March 5, 2027. What is changing

  • ,panic off → /security panic off
  • ,incidents view → /security incidents view
  • ,panic on → /security panic on
  • ,panic status → /security panic status
  • ,security audit → /security audit
  • ,antinuke → /configure feature:Anti-nuke
  • ,antinuke ban → /configure feature:Anti-nuke
  • ,antinuke mention → /configure feature:Anti-nuke
  • ,antinuke admin → /configure feature:Anti-nuke
  • ,antinuke admins → /configure feature:Anti-nuke
  • ,antinuke whitelist → /configure feature:Anti-nuke
  • ,antinuke list → /configure feature:Anti-nuke
  • ,antinuke enable → /configure feature:Anti-nuke
  • ,antinuke prune → /configure feature:Anti-nuke
  • ,antinuke mention whitelist → /configure feature:Anti-nuke
  • ,antinuke mention list → /configure feature:Anti-nuke
  • ,webhook firewall allow → /configure feature:Webhooks
  • ,webhook firewall list → /configure feature:Webhooks
  • ,webhook firewall off → /configure feature:Webhooks
  • ,security setup → @greed security setup
  • ,security settings → @greed security settings
  • ,security strict → @greed security strict
  • ,security grants → @greed security grants
  • ,security overwrites → @greed security overwrites
  • ,security hold → @greed security hold
  • ,security autopanic → @greed security autopanic
  • ,security unlock → @greed security unlock
  • ,security pingroles → @greed security pingroles
  • ,security panicmod → @greed security panicmod
  • ,security restore → @greed security restore
  • ,security hourly → @greed security hourly
  • ,security modlimit → @greed security modlimit
  • ,security modminute → @greed security modminute
  • ,security pinglock → @greed security pinglock
  • ,security ignore → @greed security ignore
  • ,security owner → @greed security owner
  • ,security rescue create → @greed security rescue create
  • ,security rescue use → @greed security rescue use

What is antinuke?

Antinuke is a system to automatically set a limit of the amount of actions your staff can do. If that limit is exceeded, the staff will be punished and you'll stay safe from any harmful actions done to your server.

Warning:

The server owner and whitelisted users are automatically exempt from antinuke restrictions. Antinuke tracks actions within a 60-second rolling window. Thresholds are per-action-type per-user (e.g., each user has their own ban counter). Antinuke must be explicitly enabled and each module must be configured separately.

Note:

Available punishments: warn, none, ban, kick, timeout (5 minutes), strip (dangerous roles only), stripstaff (staff roles only), jail. Mention protection also deletes the message that triggers it.

Warn and none (shown as Log only in /configure and on the dashboard) never act against anyone: greed logs the incident for your staff and undoes nothing. Warn also DMs the person who tripped antinuke (at most once every 10 minutes). With either one a bot an admin adds is not kicked, and mention protection leaves the message up. Use them while you get to know your staff's normal activity, then switch to a real punishment.

Antinuke from Automatic Setup

Turning on antinuke through Automatic Setup in your server, or on the onboarding page of the dashboard, watches bans, kicks, role, channel, webhook and emoji changes, bot additions and the vanity URL with the recommended limits: it trips on the 3rd ban, kick, role or channel change within a minute, the 2nd webhook change or the 5th emoji change, and on any bot addition or vanity change. Whoever trips it gets a warning. In Discord, press Antinuke options on the setup result to pick what greed watches and to choose strip, kick or ban instead. If antinuke is already on, setup leaves your settings as they are. You can change any limit later with ,antinuke or on the dashboard.

Secure your server in one click

Pick a protection level and greed sets everything up. Run ,security setup (Balanced), ,security setup relaxed or ,security setup strict, or open Security → Anti-nuke on the dashboard, choose a level and press Apply this level. greed turns on antinuke with limits for every module, turns on antiraid, applies the advanced protections for that level, creates a private security-logs channel if you have no log channel, and saves a restore point. Nothing is deleted, and you can fine-tune any setting afterwards.

LevelBest forWhat changes
RelaxedSmall or friendly serversHigher limits, no automatic lockdown, no raid pattern scan
Balanced (recommended)Most serversEvery guard on, automatic panic and restore, raid pattern scan
StrictLarge or targeted serversLower limits on every action, longer automatic panic, tighter moderator limits

The dashboard card shows which level the server is on, or custom once you change settings yourself. Only the server owner, an extra owner or an antinuke admin can run setup.

Advanced protection | free

These run on top of your antinuke modules. Antinuke must be enabled. Change them with the commands below, in Security → Anti-nuke → Advanced on the dashboard. See every setting with ,security settings. Only the server owner, an extra owner or an antinuke admin can change them. The server owner can also change them in /configure → Anti-nuke. Extra owners count as antinuke admins everywhere on this page.

  • ,security strict on: When someone adds Administrator, Manage Server, Manage Roles or another dangerous permission to any role, greed puts the old permissions back and punishes them.
  • ,security grants on: When someone gives a member a role with dangerous permissions, greed removes it and punishes them.
  • ,security overwrites on: When someone gives @everyone dangerous permissions in a channel, greed reverts the override and punishes them.
  • ,security hold on: When someone removes the jail role from a jailed member, greed puts it back and punishes them.

Guards punish with your antinuke default punishment, or jail if none is set. If no jail role is set up, greed removes the person's dangerous roles instead. Greed needs Manage Roles to undo changes.

  • ,security autopanic on: When antinuke punishes someone, greed starts panic mode by itself: it locks channels, removes dangerous permissions from roles below its own and pauses invites.
  • ,security unlock 30: End automatic panic after 30 minutes. Use off to keep it on until you run ,panic off.
  • ,security pingroles @Staff: Ping up to 5 roles in the antinuke log channel when automatic panic starts.
  • ,security panicmod on: While panic mode is on, only the server owner and antinuke admins can use moderation commands.
  • ,security restore on: After a nuke that deleted channels or roles, greed rebuilds what is missing from the latest restore point. Restore points are saved every 6 hours and never delete anything that still exists.
  • ,security hourly 10: Besides the 60-second module limits, punish anyone who takes more than 10 actions of one kind within an hour. This catches slow nukes.
  • ,security modlimit 30: Each moderator can run 30 bans, kicks, timeouts, jails and strips per hour through greed. The next one is blocked and treated as an antinuke violation.
  • ,security modminute 5: The same, per minute, to stop a moderator who goes rogue in a burst.
  • ,security pinglock 50: Lock every channel when members send 50 mentions within 30 seconds.

Use off to turn any limit off. The server owner, whitelisted users and antinuke admins are never limited.

,security ignore (channel, category or webhook ID) stops antinuke counting actions in that channel or category, or by that webhook. Run it again to stop ignoring, or with nothing to list them. Add your ticket category so ticket bots that create and delete channels are never punished. Up to 25.

,security owner @member makes someone an extra owner: antinuke never punishes them and they can change every security setting and manage antinuke admins and the whitelist, like the server owner. Owner-only features outside security (fake permissions, bot customization) stay with the server owner. Run it again to remove them; antinuke admins can run it with nobody to see the list. Only the server owner can add or remove extra owners, from the command, Security → Anti-nuke → Advanced or /configure → Anti-nuke → Extra owners. Up to 5. Bots cannot be extra owners.

The server owner can run ,security rescue create to receive a one-time key in DMs. If the owner account is ever lost, another account in the server can run ,security rescue use (key) to become an antinuke admin. The key works once and its use is posted in the antinuke log channel.

Every antinuke incident lists what the person did in the last hour before they were stopped, by name (for example "channel delete: general"), plus any panic or restore greed ran. View it with ,incidents view (ID), or open Security → Anti-nuke → Incidents on the dashboard to see every incident and every account it caught, including whole raid waves. Requires Administrator.

More protection tools

In the dashboard, open Security → Anti-nuke → Protection suite to configure mention protection, the webhook firewall and moderation approvals, manage panic mode, or run a security audit. Dashboard access requires Manage Server; changing these protections also requires the server owner or an antinuke admin. The security audit is available to anyone with Manage Server.

Antinuke also counts bans, kicks, and role creation or deletion performed through greed against the staff member running the command. When a command trips the configured protection, greed refuses it and applies the module's punishment.

Command tracking is enabled by default. Use --command on or --command off when configuring the ban, kick or role module, for example ,antinuke ban on --threshold 3 --command on.

Protect against unapproved @everyone, @here and role pings. Antinuke itself must be enabled. Only the server owner or an antinuke admin can configure this.

,antinuke mention on --threshold 3 --do timeout --roles on

The threshold is counted over 60 seconds and can be set from 0 to 50. A threshold of 0 acts on the first unapproved ping. Use --roles off to protect only @everyone and @here.

  • ,antinuke mention whitelist @member: Add or remove an exception; also accepts a role.
  • ,antinuke mention list: Show the exceptions.
  • ,antinuke mention off: Disable mention protection.

Use ,panic on during an active attack. After confirmation, greed removes dangerous permissions from roles below its own, locks channels, and pauses invites and member DMs.

Use ,panic status to check it and ,panic off to restore the permissions and reopen what panic mode closed. Ending panic remains available if Premium expires. A lockdown that was already active is left in place. Only the server owner or an antinuke admin can start or end panic mode.

Block unwanted pings or links sent through webhooks:

,webhook firewall on --mentions on --links on --delete off

Use --delete on to also delete the offending webhook. Greed needs Manage Webhooks to delete webhooks and permission to delete the offending messages.

  • ,webhook firewall allow (webhook ID or URL): Add or remove a trusted webhook that bypasses the firewall.
  • ,webhook firewall list: Show trusted webhooks.
  • ,webhook firewall off: Disable the firewall.

Only the server owner or an antinuke admin can change these settings.

Run ,security audit to get a security score and a checklist of improvements. It reviews server verification, staff permissions, bots, webhooks and your greed protections. It does not change any settings. Requires Manage Server.

Managing antinuke admins

By default, only the server owner can manage the antinuke configuration. Using this feature, you can add other users to be able to configure the antinuke settings.

Warning:

This is a risky command, as this will allow the user to be able to completely change the antinuke configuration.

,antinuke admin (@user)

To remove an antinuke admin, you simply use the same ,antinuke admin command.

,antinuke admin (@user)

You can quickly view all antinuke admins using the ,antinuke admins command.

Whitelisting users from the antinuke

By default, everyone is subject to being affected by the antinuke. To exempt a user, simply whitelist them using the ,antinuke whitelist command.

Warning:

This is a risky command, as it allows the user to completely bypass all antinuke restrictions.

,antinuke whitelist (userid)

To remove users from the whitelist, simply use the same ,antinuke whitelist command.

,antinuke whitelist (userid)

You can view all whitelisted users by using the ,antinuke list command.

Configuring the antinuke

Configure the antinuke simply by using these commands. Use ,antinuke to view the antinuke settings at anytime. Make sure to toggle on antinuke using ,antinuke enable

Setting up antinuke modules.

Antinuke has various modules that you can configure to protect your server.

Available Module

Protect your server from unauthorized administrative changes.

  • guildupdate - Changes to name, region, icon, or settings.
  • webhooks - Creation or usage of webhooks.
  • vanityurl - Changes to the server vanity URL.
  • integrationcreate - Adding new integrations/bots.
  • integrationupdate - Modifying existing integrations.
  • integrationdelete - Removing integrations.
  • Usage Example:
    ,antinuke guildupdate (status) [flags]

Prevent mass-kicks, bans, or unauthorized bot additions.

  • botadd - When a bot is added by a non-whitelisted user.
  • kick - Limits the number of members a staff can kick.
  • ban - Limits the number of members a staff can ban.
  • memberprune - Unauthorized server pruning actions.
  • Usage Example:
    ,antinuke ban (status) [flag]

Secure your server structure from deletion or manipulation.

  • rolecreate / roleupdate / roledelete

  • channelcreate / channelupdate / channeldelete

  • Usage Example (Channels):

    ,antinuke channel (status) [flags]
  • Usage Example (Roles):

    ,antinuke role (status) [flags]

Protect your server's creative assets and engagement tools.

  • emojicreate / emojiupdate / emojidelete
  • stickercreate / stickerupdate / stickerdelete
  • soundboardcreate / soundboardupdate / soundboarddelete
  • invitecreate / invitedelete
  • prune: punishes anyone who prunes members, for example ,antinuke prune on --threshold 1 --do ban
  • Usage Example:
    ,antinuke invite (status) [flags]
Note:

within the greed dashboard only

Firstly, toggle your antinuke on.

,antinuke ban (status) [flags]

Next, set the punishment for your modules.

,antinuke (module) (status) (punishment)

Now, set the threshold.

Note:

A higher threshold means the user must do more of a specific action to trigger the antinuke.

,antinuke (module) threshold (threshold)

Undoing what they did

When antinuke stops someone, greed also reverses what they did: bots they added are kicked, members they banned are unbanned, and channels, roles, webhooks, emojis, stickers, soundboard sounds, integrations and invites they created are deleted. This is on by default. Turn it off for one module with --undo off, from the module's settings on the dashboard, or in /configure. greed needs the matching permission (for example Kick Members to remove a bot).

Example
,antinuke ban on --undo off

If you want, you can view settings for a module using the following commands:

,antinuke config

Alternatively, you can simply use ,antinuke (module).

Using the dashboard assistant

You can change antinuke by chatting with the assistant in the dashboard. Ask something like "set the ban module to 3 bans and kick" or "add @Helper to the antinuke whitelist", and it shows you the exact before and after to approve before anything changes.

Turn antinuke on or off, turn modules on or off, change their thresholds, punishments and command tracking, add or remove members on the antinuke whitelist, and show you the current settings.

Only the server owner or an antinuke admin, the same people who can change antinuke with commands. Anyone else is refused, and the assistant will not show them thresholds, punishments or the whitelist.

Only the server owner can add or remove antinuke admins through the assistant.

The assistant will not help test, probe or get around antinuke. If it refuses a change, make it yourself on the dashboard page or with commands.