Protection

The anti-nuke that stops a hacked account before it empties your server

A “nuke” is a server destroyed from the inside: channels deleted one after another, roles wiped, members banned in a row. It comes from an account with permissions, a rogue moderator or, far more often, a hacked account. Orion recognizes it by its behaviour, whatever its role.

Every action counts, over 15 minutes

Orion counts each member’s sensitive actions over 15 minutes. As soon as a member goes over the limit, Orion stops them and applies the sanction you chose. An alert with the member goes to your logs, and your notification roles are mentioned.

  • Channels deleted or edited in bulk
  • Roles deleted or edited in bulk
  • Bans and kicks in a row (anti mass actions)
  • Server name, icon and settings changed: the change is reverted

You set the sensitivity and the sanction

In /settings, the malicious users detection comes down to two choices: its sensitivity and the sanction applied. Trusted members can be added to the whitelist.

Why an anti-nuke is a must

Discord permissions can’t tell a trusted moderator from an account that was just hacked: both have exactly the same rights. A scanned QR code or a fake login link is enough for a legitimate account to start deleting everything.

The anti-nuke judges actions, not roles. A legitimate moderator doesn’t delete ten channels in two minutes.

Get started

Add Orion to your server, then open /settings and adjust the malicious users detection: sensitivity and sanction.

Technical documentation

Behaviour checked in the code of Orion Shield v2.5, on October 25, 2026. Every protection is off by default.

Channel regulation

Stops a member who creates, deletes or edits channels in bulk.

How to turn it on

/settings, Suspect users section: channel regulation sensitivity, from 1 to 100% (0 to turn it off, 50% recommended).

Events watched
  • Channel creations, deletions and edits, read from the audit log, with the author of each action.
Thresholds
  • For each member, Orion Shield counts their actions over 15 minutes and computes a score: (0.8 × creations)² + (1.3 × deletions)² + (0.6 × edits)². For a bot, the coefficients go up to 2 for creations and 2.5 for deletions.
  • The score is multiplied by a seniority factor, from 1 for a long-standing member up to 2.25 for a very new account that just joined.
  • Threshold: 140 − 0.8 × sensitivity, which is 100 at the recommended 50% sensitivity.
  • In practice, at 50%: 8 channel deletions in 15 minutes for a long-standing member, 6 for a very new member, 5 for a bot.
Automatic actions
  • An alert with the member goes to your logs, and your notification roles are mentioned.
  • Default scale, for each new detection within 15 minutes: warning, then removal of sensitive roles, removal again, then ban.
  • Role removal takes away the roles carrying a sensitive permission (Administrator, ban, kick, manage channels, roles, webhooks, server…) placed below Orion Shield’s role.
  • You can replace this scale in the sanction settings, for example to remove roles on the first detection.
Exceptions
  • The server owner and Orion Shield itself are never sanctioned.
  • Whitelisted members (/whitelist) are ignored.
  • A member given a temporary bypass by an administrator is ignored while it lasts.
  • Actions made by Orion Shield itself and actions without an author in the audit log are ignored.
Required Discord permissions
  • View Audit Log.
  • Manage Roles, to remove roles.
  • Ban Members.
  • Orion Shield’s role must sit above the members to sanction: Discord doesn’t let a bot sanction a member whose highest role is equal to or above its own.
Known limits
  • Orion Shield detects from the audit log, so after the actions: deleted channels aren’t recreated. There is no automatic backup or restore.
  • With the default scale, the first detection is only a warning: the member can make one more action before losing their roles.
  • Roles managed by an integration (a bot’s role) can’t be removed.
  • A member whose role is above Orion Shield’s can’t be sanctioned.
Test scenario
  1. On a test server, set channel regulation to 50%.
  2. Give a long-standing test account a role with the Manage Channels permission, placed below Orion Shield’s role.
  3. With that account, create then delete 9 channels within 15 minutes.

Expected result

  • On the 8th deletion, a “Channels regulation” alert appears in your logs and the account gets a warning.
  • On the next deletion, the role with Manage Channels is removed.

Role regulation

Stops a member who creates, deletes or edits roles in bulk.

How to turn it on

/settings, Suspect users section: role regulation sensitivity (0 to turn it off, 50% recommended).

Events watched
  • Role creations, deletions and edits, read from the audit log.
Thresholds
  • Same calculation as for channels, with coefficients of 0.7 for creations, 1.2 for deletions and 0.6 for edits, over 15 minutes.
  • In practice, at 50%: 9 role deletions in 15 minutes for a long-standing member, 6 for a very new member.
Automatic actions
  • Same alert and same default scale as for channels: warning, removal of sensitive roles, removal, ban.
Exceptions
  • The server owner and Orion Shield itself are never sanctioned.
  • Whitelisted members (/whitelist) are ignored.
  • A member given a temporary bypass by an administrator is ignored while it lasts.
Required Discord permissions
  • View Audit Log.
  • Manage Roles.
  • Ban Members.
  • Orion Shield’s role must sit above the members to sanction: Discord doesn’t let a bot sanction a member whose highest role is equal to or above its own.
Known limits
  • Deleted roles aren’t recreated automatically.
  • Same limits as channel regulation.
Test scenario
  1. Set role regulation to 50%.
  2. With a test account that has Manage Roles, create then delete 10 roles within 15 minutes.

Expected result

  • On the 9th deletion, a “Roles regulation” alert and a warning.
  • On the next one, the account’s sensitive roles are removed.

Anti mass actions: bans and kicks

Stops a member who bans or kicks in a row, the typical move of a hacked staff account.

How to turn it on

/settings, Suspect users section: mass moderation detection sensitivity (0 to turn it off, 50% recommended).

Events watched
  • Bans and kicks, read from the audit log, with the author of each action.
Thresholds
  • For each member, over 15 minutes: (bans)² + (0.8 × kicks)², with coefficients of 1.2 and 1 for a bot.
  • The score is multiplied by the member’s seniority factor and by a server size factor: the bigger the server, the more actions it takes, since moderation happens more often there.
  • Threshold: 140 − 0.8 × sensitivity, which is 100 at 50%.
  • In practice, at 50% and for a long-standing member: 11 bans in 15 minutes on a 100-member server, 14 on 1,000 members, 18 on 10,000 members.
Automatic actions
  • Same alert and same default scale as for channels: warning, removal of sensitive roles, removal, ban.
Exceptions
  • The server owner and Orion Shield itself are never sanctioned.
  • Whitelisted members (/whitelist) are ignored.
  • A member given a temporary bypass by an administrator is ignored while it lasts.
  • Bans made by Orion Shield itself are ignored.
Required Discord permissions
  • View Audit Log.
  • Manage Roles, to remove roles.
  • Ban Members.
  • Orion Shield’s role must sit above the members to sanction: Discord doesn’t let a bot sanction a member whose highest role is equal to or above its own.
Known limits
  • Members already banned aren’t unbanned automatically: find them in the audit log and the ban list.
  • On a very large server, the higher threshold lets more actions through before detection: raise the sensitivity if needed.
Test scenario
  1. On a test server with fewer than 100 members, set mass moderation detection to 50%.
  2. Give a long-standing test account a role with the Ban Members permission, placed below Orion Shield’s role.
  3. With that account, ban 12 accounts within 15 minutes: test accounts, or IDs of users who aren’t on the server.

Expected result

  • Around the 11th ban, a “Mass moderation detection” alert appears and the account gets a warning.
  • On the next ban, the role with Ban Members is removed.

Server identity protection

Reverts changes to the server name, icon and settings.

How to turn it on

/settings, Protection section: “Anti server update”.

Events watched
  • Server update read from the audit log: name, icon, content filter, AFK channel and other settings.
Thresholds
  • Any change by a non-whitelisted member.
Automatic actions
  • Orion Shield puts the old value back.
  • Default scale: warning, then removal of sensitive roles, then ban.
Exceptions
  • The server owner and Orion Shield itself are never sanctioned.
  • Whitelisted members (/whitelist) are ignored.
  • A member given a temporary bypass by an administrator is ignored while it lasts.
  • Changes by whitelisted members are only written to the logs.
Required Discord permissions
  • View Audit Log.
  • Manage Server, to put the old value back.
  • Manage Roles and Ban Members, for the sanctions.
Known limits
  • Remember to whitelist your administrators, or their own changes will be reverted.
Test scenario
  1. Turn the protection on.
  2. With a non-whitelisted test account that has Manage Server, rename the server.

Expected result

  • The name goes back to the old value and the account gets a warning, written to your logs.

Frequently asked questions

What is a nuke on Discord?

A nuke is a Discord server destroyed from the inside by an account with the permissions to do it: channels and roles deleted one after another, members banned or kicked in a row.

What should I do if a moderator’s account was hacked?

Remove their roles right away, ask the owner to change their password and turn on two-factor authentication, then check the server’s audit log. With Orion’s anti-nuke, the account is stopped as soon as it goes over the action limit.

How do I turn on Orion’s anti-nuke?

Add Orion to your server, then adjust the malicious users detection in /settings: sensitivity and sanction.

Orion's other protections

Protect your server with Orion

Anti-raid, anti-nuke, anti-scam and AI moderation: add Orion to your Discord server and set everything up with /settings.