What Is Beast Mode in Security Bot? Server-Wide Threat Scoring Explained
Beast Mode is a free protection mode in Security Bot. It catches attacks that slip under per-user anti-nuke limits. Each protected action you give points to, such as a ban or channel delete, adds to one server-wide score. When the score reaches your limit, Beast Mode activates and punishes anyone who then performs a protected action, for about an hour.
Why anti-nuke alone is not enough
Anti-nuke counts actions per user: if the channel delete limit is three, the third delete by the same account triggers the punishment. There are two ways around that. Spread the actions across several accounts, so each stays under the limit. Or pace a single account: delete two channels, wait for the counters to reset (they reset every 10 minutes), delete two more.
Beast Mode ignores who did what. It adds up the protected actions across the server, and the score only resets once an hour while Beast Mode is inactive. Say three accounts each delete two channels. They stay under a per-user limit of three. But at two points per delete, they push the server-wide score to twelve, past a limit of ten.
How the score works
| Action | Suggested points | Why |
|---|---|---|
| Channel delete | 4 | The signature of a nuke |
| Ban | 3 | Removes members until someone unbans them |
| Role delete | 3 | Breaks permissions server-wide |
| Bot add | 3 | How nuke bots arrive |
| Kick, prune | 2 | Removes members |
| Channel create, role create | 1 | Used to spam but reversible |
| Webhook create, vanity change, Mention @everyone (Premium) | 1 to 2 | Webhook spam and defacement |
Every value is editable on the Beast Mode page and starts at 0. The threshold, labelled Score limit, is the total that activates the mode. It defaults to 40. Beast Mode only counts an action when the matching anti-nuke trigger is turned on, so check the Anti-Nuke page too.
All thirteen point values work on Premium. On Free, webhook creation, vanity changes, and @everyone mentions are not tracked, so ten apply.
What happens when Beast Mode activates
- The Beast Mode page shows it as Active. Activation is not posted to a log channel.
- From that moment, any protected action by a non-exempt user is punished immediately with the kick, ban, or clear-roles punishment you chose. No more counting. @everyone pings are the exception: Beast Mode does not punish them. Each punishment is written to the security log as User Punished, and the owner gets a DM.
- The mode stays active until an hourly check finds it has been on for an hour, so it ends 60 to 120 minutes after activation however busy the server is. Someone with dashboard access can end it sooner with Deactivate now.
- When it ends, the score goes back to 0. The end is not logged either.
Who is exempt
Exempt users are the server owner, anyone with a role above Security Bot's role, and, only if Allow whitelist bypass is on, whitelisted users and roles.
Worked example: three accounts, one nuke
This is an illustration, not a real incident. Say your anti-nuke channel delete and ban limits are 3 and your Beast Mode score limit is 10, with channel delete worth 4 points and ban worth 3. Three phished moderator accounts start at the same time, each scripted to stay under the per-user limit.
| Time | Action | Per-user count | Server score |
|---|---|---|---|
| 00:00 | Account A deletes a channel | A: 1 of 3 | 4 |
| 00:02 | Account B deletes a channel | B: 1 of 3 | 8 |
| 00:03 | Account C bans a member | C: 1 of 3 | 11, Beast Mode activates |
| 00:04 | Account A deletes a channel | A: 2 of 3 | Punished on the spot, roles cleared |
| 00:05 | Account B deletes a channel | B: 2 of 3 | Punished on the spot, roles cleared |
Without Beast Mode, each account could reach its third delete before anti-nuke acted: nine channels gone, plus the bans.
With it, the score reaches the limit after two deletes and one ban. A and B lose their roles on their very next delete: four channels gone instead of nine, and the attack stops there.
If Recovery was on, the four channels can be restored from its recently deleted list, with their permissions. The security log shows anti-nuke's User Warning entries for the first three actions and a User Punished entry for A and B.
What Discord itself provides versus what needs a bot
Discord's permission system decides who may delete a channel. It does not count how many were deleted or how fast. Required 2FA for moderators adds friction, Activity Alerts flag unusual join and DM activity, and AutoMod can time members out automatically for message rules (Custom Keyword and Mention Spam). None of these counts destructive staff actions across the server. The audit log records them after the fact.
That is the gap Beast Mode fills: one counter for the whole server with an automatic response. Native permissions still matter, because a role above Security Bot's role is exempt from every trigger. Put the bot's role at the top and keep Administrator with the owner, as described in the setup guide.
Tuning without false alarms
The dashboard includes a simulator. Enter the actions your staff perform on a busy day, for example a category cleanup of five channel deletes and two role deletes, and check the resulting score. If it activates, raise the score limit or lower the points for those actions. Then enter a nuke: ten channel deletes and five bans. It should activate within the first three or four actions.
Open Beast Mode in the dashboard
Under Protection, choose Beast Mode and turn it on. It is free on every server.
Assign points per action
Every action starts at 0 points, so nothing is counted until you set them. Give channel delete and ban the most (3 to 4), role delete, bot add, kick, and prune fewer (2 to 3), and channel or role create the least (1).
Set the score limit
Start with a Score limit of 10 to 15 (the default is 40). Nothing happens until the server-wide score reaches it.
Choose a punishment
Clear roles is the default. It strips the attacker's roles and is reversible. Kick and ban are the alternatives.
Decide on whitelist behavior
Leave Allow whitelist bypass off unless you are sure a whitelisted staff account could never be the compromised one.
Run the simulator and save
Replay a normal busy day and a nuke. Adjust until the first does not activate and the second activates within a few actions.
Recommended settings by server type
| Server type | Score limit | Points to raise | Punishment | Allow whitelist bypass |
|---|---|---|---|---|
| Small community (under 1,000) | 10 | Channel delete 4, ban 3 | Clear roles | Off |
| Public gaming server | 12 to 15 | Channel delete 4, bot add 3, webhook create 2 (Premium) | Clear roles | Off |
| Crypto, NFT, or marketplace | 10 | Ban 3, role delete 3, vanity change 2 (Premium) | Clear roles | Off |
| Server network with a large staff | 15 to 20 | Channel delete 4, ban 2 | Clear roles | On, with narrow per-action whitelist entries only |
These are starting points. A larger staff needs a higher score limit so a normal day never activates it. Run the simulator against your own staff's routine before you commit to any of them.
Common mistakes and how to fix them
- No points assigned. Every action starts at 0, so an enabled Beast Mode with default values never activates. Set points before you rely on it.
- Score limit too low for the team. A category cleanup activates Beast Mode and strips an admin's roles. Run the simulator with the real cleanup, then raise the score limit or lower the points for channel delete.
- Allow whitelist bypass on with broad whitelist entries. A phished whitelisted admin is exempt from Beast Mode for every action they are whitelisted for. Keep the bypass off, or whitelist only the actions each role really needs. See how to whitelist bots and users.
- Bot role below staff roles. Anyone above the bot is exempt, so Beast Mode cannot punish the accounts most likely to be compromised. Drag the Security Bot role to the top in Server Settings, Roles.
- No security log channel. The User Punished entries for Beast Mode punishments go nowhere. Assign the channel on the Logging page, and use the Current score card on the Beast Mode page to see how close normal days come to the limit.
- Treating Beast Mode as a replacement for anti-nuke. Beast Mode only starts punishing after the score limit. Anti-nuke stops a single fast attacker earlier. Run both.
When Beast Mode activates: first five minutes, first hour, next day
| When | What to do |
|---|---|
| First 5 minutes | Open the security log and the audit log to see which accounts acted. If it was staff doing routine work, press Deactivate now and give their roles back. If it was an attack, leave it active. |
| First hour | Strip or ban the responsible accounts, kick any bot they added, and delete webhooks they created. If Recovery was on, restore deleted channels and roles from Recently deleted on the Recovery page. Unban members from the attack window. |
| Next day | Rerun the simulator with the actual sequence from the audit log and adjust points or the score limit. Require 2FA for moderator actions and check who holds Administrator. |
The full recovery order is in how to recover a Discord server after a nuke.
What Beast Mode writes to the log
Activation and deactivation are not logged. Each account punished while Beast Mode is active gets a User Punished entry in the security log, and the owner gets a DM. Anti-nuke's User Warning entries before it show which accounts were acting and how close each was to its per-user limit.
Review these next to the anti-nuke entries. If the Current score on the Beast Mode page regularly reaches half the limit on normal days, raise the limit a little. If an incident took more than three or four actions to activate, lower the limit or raise the points for the actions that were used.
Beast Mode with the rest of Security Bot
- Anti-nuke catches the single fast attacker. Beast Mode catches the distributed or paced one. Run both.
- Recovery on Premium, if it was on before the attack, restores deleted channels, categories, roles, and emojis from its backups and recently deleted list. With Restore automatically after anti-nuke on, it also puts back what a punished account deleted in the last 30 minutes.
- Logging shows the warnings and punishments, so you can see which accounts acted and who was punished.
Do this with Security Bot
Beast Mode Discord Protection: Escalate from normal monitoring to aggressive protection when attacks become serious.
Beast Mode is Security Bot's escalation layer. Dangerous actions add the points you assign to one server-wide score. At your limit, Beast Mode activates and immediately punishes anyone who performs a dangerous action. It ends about an hour later, or when you deactivate it.
Frequently asked questions
What is Beast Mode in Security Bot?
An escalation mode that adds every protected action you give points to into one server-wide score and, once the score reaches your limit, punishes any protected action for about an hour.
Is Beast Mode free?
Yes. Every server with Security Bot can enable it.
What score limit should I start with?
With the suggested points above, 10 to 15 suits most servers. Use the simulator to check your staff's normal activity stays below it.
How do I turn Beast Mode off?
Press Deactivate now on the Beast Mode page. Otherwise it ends on its own 60 to 120 minutes after it activated.
Does Beast Mode replace anti-nuke?
No. Anti-nuke limits per user. Beast Mode watches the whole server. They cover different attack patterns.
Is Beast Mode a Discord feature?
No. It is a Security Bot module. Discord has no server-wide counter for staff actions. Its audit log records them after the fact.
What if Beast Mode punished a staff member by mistake?
Press Deactivate now, give the roles back if the punishment was clear roles, then rerun the simulator with the actions from the audit log and adjust the score limit or points.
How this guide was made: drafted with AI assistance, then checked against Security Bot's source code and Discord's official help articles. Spotted something out of date? Tell us in the support server.