Real-time antinuke and antiraid for Discord. Sub-second response, fully configurable, every protection independent.Antinuke e antiraid in tempo reale per Discord. Risposta sotto il secondo, completamente configurabile, ogni protezione indipendente.
FeaturesFunzionalità
Stops mass bans, kicks, channel and role deletions and rogue bots in milliseconds — and undoes the damage.Ferma ban e kick di massa, eliminazione di canali e ruoli e bot non autorizzati in millisecondi — e annulla il danno.
Spam, mention floods, unauthorized links, join floods and ghost pings handled per user, in real time.Spam, mention flood, link non autorizzati, join flood e ghost ping gestiti per utente, in tempo reale.
One command locks every channel and kicks new joins. Lift it and everything is restored.Un comando blocca ogni canale e kicka i nuovi ingressi. Lo togli e torna tutto com'era.
SetupSetup
Invite Aura with Administrator and place its role at the top.Invita Aura con permesso Administrator e metti il suo ruolo in cima.
Pick a log channel and whitelist your trusted admins.Scegli il canale log e aggiungi in whitelist gli admin fidati.
Defaults are tuned for most servers. Tweak anything with /settings.I valori predefiniti vanno bene per la maggior parte dei server. Modifica tutto con /settings.
Why AuraPerché Aura
Every protection has its own switch, limit and punishment. Changing one never affects another, so you tune the bot exactly to your server.Ogni protezione ha il suo interruttore, il suo limite e la sua punizione. Cambiarne una non tocca le altre: configuri il bot esattamente come serve al tuo server.
Events are processed the moment they arrive. Most attacks are cut off in under 500ms, before real damage is done.Gli eventi vengono elaborati appena arrivano. La maggior parte degli attacchi viene fermata in meno di 500ms, prima che faccia danni veri.
The server owner is never touched by any protection. Trusted admins can be whitelisted in a single command.Il proprietario del server non viene mai toccato da nessuna protezione. Gli admin fidati si aggiungono in whitelist con un solo comando.
Message content is checked in memory only and never stored. We keep just your configuration and whitelisted IDs.Il contenuto dei messaggi è controllato solo in memoria e mai salvato. Conserviamo solo la configurazione e gli ID in whitelist.
★ Premium
9 advanced protections, extended logs, Panic Mode and verification gates.9 protezioni avanzate, log estesi, Panic Mode e sistemi di verifica.
FAQ
Yes, the full Anti-Nuke and Anti-Raid suite is free. Premium adds advanced protections and extended logs.Sì, tutta la suite Anti-Nuke e Anti-Raid è gratuita. Il Premium aggiunge protezioni avanzate e log estesi.
Administrator, with its role placed above the roles it needs to act on. See the Permissions page in the docs.Administrator, con il suo ruolo sopra i ruoli su cui deve agire. Vedi la pagina Permessi nella documentazione.
Never. The owner is unconditionally immune from every protection.Mai. Il proprietario è incondizionatamente immune da ogni protezione.
No. Content is checked in memory for spam, links and ghost pings, and is never written to the database.No. Il contenuto viene controllato in memoria per spam, link e ghost ping e non viene mai scritto nel database.
Aura Security is a Discord bot built specifically to protect servers from two categories of threat: nuke attacks from compromised admins, and coordinated raids from outside. It acts in real time — most responses happen in under 500ms from the moment an event is received.
A nuke attack happens when an admin account is compromised — by token theft, phishing, or a malicious bot — and the attacker uses that account's permissions to mass-ban members, delete channels, delete roles, or add unauthorized bots. Because the actions come from a trusted account, Discord's own permission system doesn't stop them. Aura Security monitors admin-level events and cuts off the attack the moment a configured limit is exceeded, before significant damage is done.
A raid happens when a group of users — often using bot accounts — floods a server with spam messages, mention spam, unauthorized invite links, or simply joins the server in mass to cause chaos. Aura Security detects these patterns and responds per-user before the flood overwhelms the server.
Every protection is independent. Each one has its own on/off state, its own limit, and its own configured punishment. Changing the punishment for Anti Ban has no effect on Anti Kick. Disabling Anti Link has no effect on Anti Spam. This means you can fine-tune the bot precisely for your server without trade-offs.
When an event is detected, the bot checks three things in order before doing anything: is the user the server owner (always immune)? Is the user in the whitelist (always immune)? Does the user have Administrator or Manage Server permissions (immune from Anti Raid only)? If none of those apply, the bot checks the limit for that specific action. If the limit is exceeded, the configured punishment is applied immediately — no confirmation, no delay.
Watches admin-level actions: mass bans, mass kicks, channel and role deletions, unauthorized bot additions, webhook creation, server renames. Tracks each action type in a 60-second window per executor. Punishes the executor and undoes the damage where possible (auto-unban, channel cleanup, permission restore).
Watches member behavior and joins: message spam, mention floods, unauthorized links, join floods, ghost pings, new accounts. Works on a per-user, per-message, and per-join basis in real time. Escalates automatically to lockdown when join flooding is detected at scale.
Only the person who ran the command sees the response. Security events are sent separately to the configured log channel, so the rest of your members never see bot alerts cluttering channels.
Everything you need to do after adding the bot, in the right order. The whole process takes under 5 minutes.
Make sure Aura Security has the Administrator permission and that its role is positioned above all other roles in Server Settings → Roles. Without this, punishments will silently fail on higher-ranked users.
Create a private channel (e.g. #aura-logs) visible only to staff. Every detection, punishment, lockdown, and ghost ping will be sent here.
If you skip this, Aura will attempt to find a channel named aura-logs or log automatically.
The server owner is always immune automatically. Every other staff member who performs admin actions (deleting channels, kicking users, etc.) must be whitelisted or the bot may detect their actions as an attack.
Run this for every trusted admin. Takes effect immediately for all protections.
Default punishment for all Anti Nuke protections is Ban. If you prefer Kick or Derank for certain actions, change them now. Anti Raid actions default to timeout for spam and mention spam, and kick for join flooding.
Select the action and the punishment. Changes apply immediately and persist across restarts.
The defaults work for most servers. Adjust only if you get false positives (active chat servers) or want stricter protection.
| Protection | Default | Recommended for active servers |
|---|---|---|
| Anti Spam | 5 msg / 3s | 8–10 msg / 3s |
| Anti Mention | 5 mentions / msg | 8–10 mentions / msg |
| Anti Join Flood | 10 joins / 10s | 15–20 joins / 10s |
These are off by default because they require additional configuration or are too strict for general use:
| Protection | What to do |
|---|---|
| Anti Link | Enable, then run /antiraid link add for each domain you want to allow (e.g. youtube.com, twitch.tv). Discord invites are always blocked regardless.
|
| Account Age | Run /antiraid accountage 7. New accounts younger than 7 days are kicked on join. Adjust the number based on your community. |
| Anti Ghost Ping | Enable with /enable Anti Ghost Ping. Log-only — no punishment applied, just a record in the log channel. |
Shows 3 embeds covering every protection: Anti Nuke (status, limit, punishment), Anti Raid (thresholds, actions), System (log channel, whitelist count, raid mode). Check this before your server goes live.
Aura Security is now configured. The bot will protect your server 24/7. Keep the log channel monitored to stay aware of suspicious activity.
Anti Nuke monitors destructive admin-level actions and responds immediately when a limit is exceeded. Each protection has its own independent counter, window, and punishment.
When an executor performs a tracked action, a counter starts for that executor and that specific action type. The counter resets 60 seconds after the last event. If the counter reaches the configured limit within that window, the punishment is applied immediately.
Anti Ban limit = 3. User bans member #1 at 12:00:00 (counter: 1/3). Bans #2 at 12:00:15 (2/3). Bans #3 at 12:00:45 (3/3) → limit reached, punishment applied immediately. The victim of each ban is also auto-unbanned. Counter resets at 12:01:45 (60s after last event).
| Protection | Triggered by | Extra action on detection | Default |
|---|---|---|---|
Anti Ban |
Any member ban | Auto-unbans the victim immediately | 5/min |
Anti Kick |
Any member kick | — | 5/min |
Anti Role Delete |
Role deletion | — | 3/min |
Anti Role Create |
Role created with dangerous permissions | Removes the dangerous permissions from the new role immediately | 8/min |
Anti Channel Delete |
Channel or category deletion | — | 3/min |
Anti Channel Create |
Channel creation (flood) | Deletes the created channels when the limit is hit | 8/min |
Anti Bot Add |
Unauthorized bot added to server | Kicks the bot immediately | immediate |
Anti Prune |
Member prune executed | — | immediate |
Anti Role Update |
Role permissions changed to dangerous values, or permissions stripped | Restores the previous permissions immediately | 3/min |
Anti Webhook |
Unauthorized webhook created | Deletes the webhook immediately | immediate |
Anti Guild Update |
Server name changed without authorization | Restores the original name immediately | immediate |
The following users are completely exempt from all Anti Nuke checks: the server owner (unconditionally), users added to the whitelist via /whitelist add. Users with Administrator or Manage Server permissions are not automatically exempt from Anti Nuke — whitelist them explicitly if needed.
The bot reads Discord's Audit Log to find who performed each action. Discord typically populates the audit log within 1–3 seconds of an event. If the bot cannot find the executor within 3 seconds, it logs the event but cannot apply a punishment. This is a Discord API limitation.
Commands to enable, disable, and configure each Anti Nuke protection independently.
Enables a specific protection. All Anti Nuke protections are enabled by default — use this only if you previously disabled one.
Disables a specific protection. The protection will no longer monitor or act on that action type.
Changes how many actions per minute are allowed before punishment triggers. Lower = stricter. Protections with "immediate" default (Anti Bot Add, Anti Prune, Anti Webhook, Anti Guild Update) do not use a limit.
Each Anti Nuke protection has its own punishment, configured independently. The punishment is applied to the executor the moment the limit is exceeded.
| Type | What it does | Reversible? |
|---|---|---|
Ban |
Permanently bans the executor from the server | Yes — unban from Discord settings |
Kick |
Removes the executor from the server. They can rejoin if they have an invite. | Yes — they can rejoin |
Derank |
Removes all roles from the executor, leaving them with no permissions. They stay in the server. | Yes — reassign roles manually |
Ban is the default and the most effective — the attacker is immediately removed and cannot rejoin. Use this for protections where an attack is clearly malicious (Anti Ban, Anti Bot Add, Anti Prune, Anti Webhook).
Kick is less severe and useful when the executor might be a legitimate admin who made a mistake, or when you want to give them a chance to explain themselves.
Derank is the most conservative option — the executor loses all power immediately but stays in the server. Useful when you want to investigate before deciding on a permanent action.
Change the punishment for a specific action. Applied immediately and persists across bot restarts.
The server owner receives a DM only when a punishment is actually applied — not when an action is detected and monitored below the limit. Every detected event (including below-limit ones) is always logged in the log channel.
Anti Raid protects against attacks that come from outside the server — coordinated spam, mass joins, unauthorized links, and new accounts. Each check is independent and processes events in real time.
| Protection | How it triggers | Default |
|---|---|---|
Anti Spam |
User sends more than N messages in 3 seconds in any channel | ON 5 msg/3s · timeout |
Anti Mention |
A single message contains more than N user mentions. @everyone and @here count as 10 mentions each. | ON 5/msg · timeout |
Anti Join Flood |
More than N members join in 10 seconds. Triggers Auto Lockdown if enabled. | ON 10/10s · kick |
Auto Lockdown |
Activates a 5-minute lockdown automatically when Anti Join Flood triggers | ON |
Anti Link |
A message contains a URL not in the allowed domain list. Discord invite links are always blocked regardless of the list. | OFF |
Account Age |
A new member joins with an account younger than N days | OFF 7 days |
Anti Ghost Ping |
A message containing user mentions is deleted within a few seconds of being sent | OFF log only |
Raid Mode |
Manual toggle — every member who joins while active is kicked or banned | OFF |
The following users are exempt from all Anti Raid checks: the server owner, whitelisted users. Users with Administrator or Manage Server permissions are automatically exempt from Anti Spam, Anti Mention, Anti Link, and Anti Ghost Ping — but not from Anti Join Flood, Account Age, or Raid Mode.
The bot tracks every message per user in a 3-second sliding window across all channels. If the count exceeds the threshold, the spam messages are deleted and the action is applied. The window resets after 3 seconds of silence. The default action is a 10-minute timeout — the user cannot send messages but stays in the server.
Raid Mode is a manual emergency toggle. When active, every member who joins is immediately kicked or banned — no threshold, no delay. The server owner and whitelisted users are immune. Run /raidmode again to deactivate it. Use this during an active raid when the join flood has already been stopped by lockdown but members are still trying to join.
Commands to configure all Anti Raid protections, thresholds, and emergency modes.
Sets the spam threshold and action. The bot deletes the spam messages regardless of the action chosen.
Sets the mention spam threshold and action. The message is deleted on detection.
Sets the join flood threshold and action. When triggered, Auto Lockdown also activates if enabled.
Manages the domain whitelist for Anti Link. Enable Anti Link first with /enable Anti Link. Discord invite links are always blocked regardless of this list.
Sets the minimum account age and enables Account Age check automatically. New members whose Discord account is younger than this number of days are kicked immediately on join.
Toggles Raid Mode on or off. When active, every joining member is immediately kicked or banned. Run the command again to deactivate. Whitelisted users and the server owner are always immune.
Commands to manage Discord's built-in server security settings directly, without opening Server Settings.
Sets the server verification level. Works on all server types. Higher levels reduce bot account and alt account raids.
| Level | Requirement to send messages |
|---|---|
None |
No restrictions |
Low |
Must have a verified email on their Discord account |
Medium |
Must have been registered on Discord for at least 5 minutes |
High |
Must be a member of the server for at least 10 minutes |
Highest |
Must have a verified phone number on their Discord account |
Sets the explicit content filter level. Community servers only. When active, Discord automatically scans and removes media that violates its guidelines.
Pauses or resumes all invite links. When paused, no one can join via any existing invite link — including permanent ones. Community servers only.
Shows current server security settings: verification level, content filter status, MFA requirement for moderators, invite state, total members, and whether Community mode is enabled.
Content filter and invite pausing require Community mode. Enable it in Server Settings → Enable Community. /server info will tell you if your server is a Community server.
Exempt specific users from every Aura Security protection — both Anti Nuke and Anti Raid.
Whitelisted users are completely ignored by all checks, regardless of what they do. The server owner is always exempt without needing to be added to the list.
Users with Administrator or Manage Server permissions are automatically exempt from Anti Spam, Anti Mention, Anti Link, and Anti Ghost Ping. However, they are not exempt from Anti Nuke protections. If a trusted admin needs to perform bulk admin actions (e.g. deleting many channels at once), whitelist them explicitly.
Adds a user to the whitelist. Takes effect immediately for all protections and persists across restarts.
Removes a user from the whitelist. They will be monitored by all protections again immediately.
Shows all users currently in the whitelist with their Discord IDs. The server owner is not shown here — they are always exempt regardless.
Silence every text channel in seconds. Use during an active raid or emergency to prevent members from communicating.
Lockdown removes Send Messages, Add Reactions, and Create Thread from @everyone across all text channels. It does not affect voice channels or stage channels. Channels that had those permissions explicitly denied before lockdown are not changed.
Activates lockdown immediately across all text channels. A message is sent to the log channel with who triggered it and why.
Lifts the lockdown and restores permissions to all channels. Can be used before the duration expires.
When Anti Join Flood triggers and Auto Lockdown is enabled, lockdown activates automatically for 5 minutes. The log channel receives a message explaining what triggered it. You can still lift it manually with /lockdown off at any time.
General commands for monitoring, configuration, and diagnostics.
Shows the full configuration panel across 3 embeds. Embed 1 — Anti Nuke: every protection with its status (ON/OFF), current limit, and configured punishment. Embed 2 — Anti Raid: all thresholds, actions, and enabled state. Embed 3 — System: log channel, whitelist count, raid mode status, auto lockdown status.
Sets the channel where all security alerts are sent. Every detection, punishment, lockdown activation, and ghost ping is logged here. Only the active event is logged — the bot does not send a message for every monitored action below the limit.
Shows bot health: roundtrip latency, WebSocket ping (Discord API connection), uptime, total servers the bot is in, and total users across all servers.
Lists all available commands grouped by category (Anti Nuke, Anti Raid, Lockdown, Server, Whitelist, Utility) with a brief description of each.
Every server starts with this configuration. Nothing needs to be changed for the bot to be effective — defaults are calibrated for general use.
| Protection | Status | Limit | Punishment |
|---|---|---|---|
| Anti Ban | ON | 5/min | Ban |
| Anti Kick | ON | 5/min | Ban |
| Anti Role Delete | ON | 3/min | Ban |
| Anti Role Create | ON | 8/min | Ban |
| Anti Channel Delete | ON | 3/min | Ban |
| Anti Channel Create | ON | 8/min | Ban |
| Anti Bot Add | ON | immediate | Ban |
| Anti Prune | ON | immediate | Ban |
| Anti Role Update | ON | 3/min | Ban |
| Anti Webhook | ON | immediate | Ban |
| Anti Guild Update | ON | immediate | Ban |
| Protection | Status | Threshold / Setting | Action |
|---|---|---|---|
| Anti Spam | ON | 5 msg / 3s | timeout 10min |
| Anti Mention | ON | 5 mentions / msg | timeout 10min |
| Anti Join Flood | ON | 10 joins / 10s | kick |
| Auto Lockdown | ON | — | 5 min lockdown on flood |
| Anti Link | OFF | — | — |
| Account Age | OFF | 7 days min | kick |
| Anti Ghost Ping | OFF | — | log only |
| Raid Mode | OFF | — | kick |
What Aura Security needs to function and why each permission is required.
Aura Security requires Administrator. This single permission is necessary because the bot needs to: read audit logs (to identify who performed actions), ban and kick members, manage roles (for Derank and Anti Role Update), manage channels (for lockdown and Anti Channel Create cleanup), and send messages to the log channel.
The bot's role must be higher than any role it needs to act on in the role hierarchy. Discord prevents a bot from banning, kicking, or modifying users whose highest role is equal to or above the bot's role. Move the Aura Security role to the top of the list (below the server owner role).
| Action | Bot role must be |
|---|---|
| Ban / Kick a user | Above the user's highest role |
| Derank a user | Above every role being removed |
| Modify a role | Above the role being modified |
| Timeout a user | Above the user's highest role |
| Action | Details |
|---|---|
| Store message content | Checked in memory only for spam/link/ghost ping detection — never written to the database |
| Change server settings without a command | Server settings are only modified via explicit /server commands run by an authorized user |
| Act on the server owner | The server owner is unconditionally immune from every action the bot can take |
| Share data with third parties | See the Privacy Policy for full details on data collection |
Specific problems, their causes, and exactly how to fix them.
Slash commands register globally and can take up to 1 hour to appear after the bot joins a new server. If it's been longer, make sure the bot was invited with the application.commands scope — re-invite using the link on the homepage. Do not delete and re-add the bot repeatedly, as this resets the registration timer.
This happens when an admin performs multiple admin actions quickly (e.g. reorganizing channels, bulk-deleting roles) and their action count hits the Anti Nuke limit. Fix: run /whitelist add @admin for all trusted staff. If someone was wrongly banned, unban them from Server Settings → Bans, then whitelist them.
The bot reads Discord's audit log to identify the executor. If the audit log is not populated within 3 seconds of the event (a Discord API delay), the executor cannot be identified and no punishment is applied. The event is still logged in the log channel. This is not a bug — it is a Discord API limitation that affects all bots.
The user's highest role is above or equal to the bot's role. Go to Server Settings → Roles and drag the Aura Security role above all other roles (except the server owner's). The server owner can never be punished by any bot regardless of role position.
If the bot restarts while a lockdown is active, the auto-release timer is lost. Use /lockdown off to lift it manually. To avoid this, keep the bot's hosting environment stable.
Raise the spam threshold: /antiraid spam threshold:8 (or higher). The default of 5 messages in 3 seconds is appropriate for average servers but can be too strict for very active gaming or community servers. Alternatively, add active users to the whitelist if they're trusted regulars.
Aura Security needs permission to View Channel and Send Messages in the log channel. If the channel is private, make sure the Aura Security role has these permissions explicitly granted on that channel. Re-run /setlog after fixing the permissions.
Join the support server. Describe what you expected to happen, what actually happened, and paste the relevant log from your log channel.
Questions about the bot's behavior and edge cases.
No. The server owner is always immune from every protection, unconditionally. This cannot be changed or overridden.
No. Message content is checked in memory only for spam detection (message count), link detection (URL check), and ghost ping detection (on deletion). Nothing is written to the database. See the Privacy Policy for the full list of what is and is not stored.
A DM is sent to the server owner only when a punishment is actually applied. If an event is detected and the executor is below the limit (being watched), only the log channel receives a message — no DM. This prevents notification spam during normal server activity.
Yes. Derank removes all roles from the executor but leaves them in the server. You can investigate what happened, then manually re-assign roles if you determine the action was a mistake. This makes Derank the safest option for ambiguous situations.
No. Anti Ghost Ping only logs the event in the log channel. No action is taken on the user. It is designed as an awareness tool — staff can see that a ghost ping happened and who did it, then decide manually whether to take action.
Administrator, Manage Server, Ban Members, Kick Members, Manage Roles, Manage Channels, Manage Webhooks, and Mention Everyone. If a role is created with any of these, Anti Role Create removes them immediately and logs the event. The creator is still punished if they've hit the limit.
Aura Security Premium unlocks advanced protections and extended logging starting from €3.99/month.
Premium features are completely independent from the base protections. They can be configured individually with /premium-setup and are visible in /settings as a dedicated 4th embed. The server owner is the only one who can configure premium features.
| Feature | What it does |
|---|---|
| Advanced Anti-Spam | Blocks duplicate messages, CAPS flood, emoji flood, and integrated app messages |
| Anti-Link Timeout | Applies a configurable timeout (1–1440 min) instead of just deleting the message |
| Ghost Ping Timeout | Punishes ghost pings with a configurable timeout instead of just logging |
| Anti-Mention Protection | Blocks mentions of specific protected users and roles, with timeout |
| Anti Server Icon Change | Detects and logs any change to the server icon |
| Anti Emoji | Protects the server's custom emoji library |
| Panic Mode MODIFIED | Emergency server lockdown and role restriction |
| Audit Logs | Separate log channel + toggle events |
| Verification System NEW | Button or captcha verification gates to stop raids |
| Custom Bot NEW | Guild-specific nickname and avatar personalization |
Configure all premium features. Visible and usable only in premium servers, only by the owner.
Shows the setup guide for all premium features. Premium servers only, owner only.
Shows the current premium status of the server — whether it's active and when it expires. Owner only.
Shows all premium features and pricing. Available to everyone, in all servers.
Pricing, the full feature comparison, and an FAQ all live on the dedicated Premium page.
Premium is activated by the Aura team. Contact us on the support server to purchase.
Four additional spam detection layers on top of the base anti-spam: duplicate messages, CAPS flood, emoji flood, and integrated app blocking.
| Layer | Triggers when | Action |
|---|---|---|
| Duplicate | Same message sent 3+ times in the last 5 messages | Delete + timeout |
| CAPS | Message 8+ chars with 70%+ uppercase letters | 3 violations → delete + timeout |
| Emoji flood | Message with more than 5 emoji | 3 violations → delete + timeout |
| App/Webhook | Message from an integrated app or unauthorized webhook | Delete immediately |
Enable or disable advanced anti-spam and toggle each layer individually.
Applies a configurable timeout instead of just deleting. Now accepts natural time formats like 1m, 1h, 1d.
This works alongside the base Anti-Link — the base Anti-Link must be enabled for this to function. The domain whitelist configured with /antiraid link add is shared between both. Discord invite links are always blocked regardless.
Enable and configure the timeout duration for anti-link violations.
Upgrades the base ghost ping detection from log-only to an active punishment. Now accepts natural time formats like 1m, 1h, 1d.
A ghost ping is when a user mentions someone and then immediately deletes the message. The bot detects the deletion and checks if the deleted message contained user or role mentions. If it did, the timeout is applied.
Enable and configure the timeout duration for ghost pings.
Protect specific users and roles from being mentioned. When a protected user or role is tagged, the message is deleted and the sender receives a timeout.
This works independently from the base Anti-Mention (which limits total mentions per message). Use this to protect staff, important roles, or users who are frequently targeted by harassment.
Manage the protected list and configure timeout duration.
Detects and logs any change to the server icon. When the icon is changed, an alert is immediately sent to the log channel with a link to the old and new icon.
This is a log-only protection — no automatic action is taken on the executor. It works alongside Anti Guild Update (which detects server name changes) to give you full visibility over unauthorized server modifications.
Enable or disable server icon change detection.
Extended security logging with more context and details on every security event — who triggered it, what exactly happened, and additional metadata.
Advanced logs provide deep visibility into every security event: Anti Nuke detections include the full audit log entry and executor history; Anti Raid events include message content previews and per-user action counts; premium events include all available metadata. Every embed gets a detailed footer with server member count and event ID.
Protects the server's custom emoji library from unauthorized changes. Detects when a compromised admin deletes, renames, or creates emojis and punishes them immediately.
| Event | Description |
|---|---|
| Emoji Delete | An emoji is removed from the server by an unauthorized executor |
| Emoji Rename / Edit | An emoji's name is changed |
| Emoji Create | An emoji is added to the server |
The server owner and whitelisted users are always immune. This protection monitors for actions by non-whitelisted admins.
Enable and configure the punishment for unauthorized emoji changes.
The nuclear option. One command instantly locks the entire server — every channel, every join, everything. Use when a situation is out of control and you need to stop all activity immediately. Now a standalone command.
| Action | Effect |
|---|---|
| All text channels | Send Messages, Add Reactions, Create Threads, Use App Commands all denied for @everyone |
| All voice channels | Connect denied for @everyone |
| New joins | Every member who joins while Panic Mode is active is immediately kicked |
| On deactivation | All channel permissions are fully restored to their previous state |
Panic Mode affects every member in the server including normal users. It is designed for genuine emergencies. Always deactivate it when the threat is resolved.
Toggle Panic Mode on or off. The executor's ID and timestamp are logged. Can only be used by the server owner.
Configure two dedicated channels to separate your server's utility events from moderation actions.
| Category | Tracked Events |
|---|---|
| Activity logs | Deleted messages, Edited messages, Nickname/role changes, Invites, Emoji |
| Audit logs | Bans, Kicks, Timeouts, Moderation actions |
Configure the dedicated channels for both activity logs and audit logs.
Disable premium logs and remove the configured channels.
Shows the current configuration and channels for premium logs.
For best organization, we recommend creating a #utility-logs channel for Activity Logs and a separate #moderation-logs channel for Audit Logs.
Set up a verification gate to protect your server from raid bots. Users must verify to get access to channels.
| Type | Description |
|---|---|
| Button (Instant) | Users verify instantly by clicking a button. Completely free. |
| Captcha (Premium) | Users must solve a generated image captcha. Requires Premium. |
Configure the verification channel, verified role, verification type, and optional unverified role.
Sends the persistent verification button panel to the configured verification channel.
View current verification configuration.
Disables the verification system.
Personalize Aura Security's name and avatar specifically in your server to match your community branding. Requires the Custom Bot tier.
| Feature | Description |
|---|---|
| Guild Nickname | Set a custom nickname for the bot in your server. |
| Guild Avatar | Upload an image as the bot's custom avatar for your server. |
Configure the custom nickname and/or avatar. Can only be executed by the server owner.
Restores the bot's default nickname and avatar in your server.
Last updated: January 2026
By adding Aura Security to your Discord server, using any of its commands, or interacting with it in any way, you agree to these Terms of Service in full. If you do not agree with any part of these terms, you must remove the bot from your server immediately.
You must be at least 13 years old to use Aura Security, in compliance with Discord's own Terms of Service. By using the bot, you represent that you meet this age requirement and have the legal capacity to enter into these terms. Server owners are responsible for ensuring their server complies with applicable laws and Discord's guidelines.
Aura Security is provided exclusively for server protection and moderation purposes. You agree to use it only in good faith and in compliance with Discord's Terms of Service and Community Guidelines. You may not use Aura Security to:
The server owner is solely responsible for how Aura Security is configured and used on their server. All actions taken by the bot — banning, kicking, timing out, or silencing members — are the direct result of the configuration set by the server's administrators. We are not liable for:
We aim to keep Aura Security available and functioning at all times, but we do not guarantee uninterrupted availability. The service may be temporarily unavailable due to planned maintenance, updates, infrastructure issues, or events outside our control. We will announce significant planned downtime in the support server when possible.
We reserve the right to modify, update, or discontinue any feature of Aura Security at any time, including but not limited to adding new protections, changing default values, removing features, or altering command behavior. Significant changes will be announced in the support server. Continued use of the bot after changes have been made constitutes acceptance of the updated service.
We reserve the right to remove Aura Security from any server at any time, without prior notice, if the server or its administrators are found to be in violation of these terms, Discord's Terms of Service, or applicable law. You may remove the bot from your server at any time by kicking it — no further action is required.
Aura Security is provided "as is" and "as available" without any warranties of any kind, expressed or implied. We do not guarantee that the bot will detect or prevent all attacks, respond within any specific timeframe, or function without errors. Security is inherently probabilistic — no automated system can catch every threat. Server owners should maintain their own moderation practices alongside the bot.
To the maximum extent permitted by applicable law, we shall not be liable for any indirect, incidental, special, or consequential damages arising out of or in connection with your use of Aura Security, including but not limited to loss of members, data, server reputation, or revenue — even if we have been advised of the possibility of such damages.
We may update these Terms of Service at any time. Changes will be announced in the support server. The date at the top of this page reflects the most recent revision. Continued use of the bot after the updated terms are published constitutes acceptance of those terms.
All premium purchases are final and non-refundable. No refunds will be issued under any circumstance, including but not limited to: accidental purchases, unused subscription time, server closure, dissatisfaction with features, or removal of the bot. By purchasing Aura Security Premium, you explicitly acknowledge and accept this policy.
Questions about these terms? Join oursupport server.
Last updated: January 2026
This Privacy Policy explains what data Aura Security collects, why it collects it, how it is used and stored, and what rights you have regarding that data. We are committed to collecting only what is strictly necessary to operate the bot and never using your data for any purpose beyond that.
We collect the minimum data required to operate the bot's security features:
/whitelist add. No other user IDs are stored.The following data is processed in memory to operate specific protections, but is never written to any database or log:
All collected data is used exclusively to operate Aura Security's protection features for your specific server. Specifically:
We do not use your data for advertising, analytics, machine learning, profiling, or any purpose beyond operating the bot. We do not sell, rent, trade, or share your data with any third parties for commercial purposes.
Configuration data is stored in a secure database. We take reasonable technical measures to protect stored data from unauthorized access, alteration, or loss. Data is retained for as long as the bot remains in your server. Removing the bot does not automatically delete your server's stored configuration — see Section 6 for deletion requests.
You have the right to request deletion of all data associated with your server at any time. To do so, contact us in the support server. We will process the request and confirm deletion. Note that deleting server data will reset all configurations — if you re-add the bot afterward, it will start with default settings.
Individual users can request removal of their User ID from a server's whitelist by asking the server owner to run /whitelist remove.
Aura Security interacts with the Discord API to function. All interaction with Discord is subject to Discord's Privacy Policy. We have no control over how Discord processes data on their end. Beyond Discord, we do not use any third-party analytics, tracking, or advertising services.
We may update this Privacy Policy from time to time. When we do, the date at the top of this page will be updated to reflect the most recent revision. Significant changes will be announced in the support server. Continued use of the bot after an updated policy is published constitutes acceptance of that policy.
Privacy requests or questions? Join oursupport server.
Last updated: April 2026
Real-time operational metrics for the Aura Security bot.