Moderation & Security

NexaBot's moderation stack is made of three layered systems: AutoMod for day-to-day rule enforcement, anti-raid for mass-join events, and anti-nuke for abusive admin-level actions — plus a full set of manual moderation commands for staff.

Moderation commands

Command	What it does
/ban	Ban a member, optionally deleting their messages from the past 0–7 days
/tempban	Ban a member for a set duration (e.g. 1h, 2d, 30d), lifted automatically
/kick	Kick a member
/mute	Timeout a member for a duration (e.g. 10m, 1h, 1d — max 28 days)
/unmute	Remove an active timeout
/warn	Warn a member with a reason, added to their case history
/warnings	View a member's warning history
/clearwarns	Clear all warnings for a member
/case	Look up a specific moderation case by number, or all cases for a member
/banlist	View all currently banned members
/purge	Bulk-delete 1–100 messages, optionally filtered to one member
/lock / /unlock	Lock or unlock a channel
/slowmode	Set a channel's slowmode delay, up to 6 hours
/nick	Change a member's nickname, or reset it

AutoMod & warn ladders

AutoMod watches for rule violations and escalates automatically using a warn ladder — a configurable sequence of consequences that gets more severe the more times a member breaks the rules. A typical ladder might look like:

Offense	Consequence
1st	Warning logged, member notified
2nd	Timeout
3rd	Kick
4th+	Ban

The exact thresholds and consequences are configurable per server in the Nexa Dashboard.

Anti-nuke

Anti-nuke protects against a compromised or malicious admin account causing mass damage. It watches for a burst of specific dangerous actions within a short window and can automatically strip permissions or ban the account responsible.

Tracked action types, each with its own configurable threshold (actions allowed within a 6-second window before triggering a response):

Action type	What it watches
Channel Delete	Bulk channel deletion
Channel Create	Bulk channel creation (often used to spam or bury real channels)
Role Delete	Bulk role deletion
Ban	A burst of bans in a short window
Kick	A burst of kicks in a short window
Webhook Create	Unauthorized webhook creation, a common attack vector for spam raids
Dangerous Permission Grant	Granting a role admin-level permissions
Channel Permission Edit	Mass permission changes across channels

Anti-nuke also supports:

• Blocking unauthorized bot additions — toggle whether new bot accounts can be added to the server at all
• A whitelist of trusted users (typically co-owners or senior staff) who are exempt from anti-nuke actions, so their legitimate bulk changes don't trigger a false positive

Panic Mode

Panic Mode is an emergency command for when a server is actively under attack. Running it immediately:

• Locks every channel
• Pauses all active invites
• Kicks recently-created accounts (a common signal of a bot raid)
• Alerts all staff

A separate command reverses the lockdown once the situation is resolved.

Honeypot

A honeypot is a designated trap channel — one that looks normal but that no legitimate member should ever post in. Any message sent there is treated as a strong signal of a bot or bad actor and triggers an automatic strike.

Link approval

For servers that want to review outside links before they're visible, NexaBot can hold links sent by non-staff for approval — staff see an approve/deny prompt, and the link is only reposted once approved. Repeated denials for the same member can escalate automatically.

Anti-raid

Anti-raid looks for patterns typical of a coordinated raid — specifically, a configurable number of joins within a 10-second window (8 by default) — and can automatically kick suspected raiders or lock the server until it's reviewed.

Staff command abuse tracking

NexaBot also tracks patterns of command usage by staff members themselves, flagging unusual spikes (for example, a moderator issuing an unusually high number of bans in a short window) so server owners can review it.

Case history

Every moderation action — warns, timeouts, kicks, bans — is logged to a per-member case history, viewable from the mod-log channel or the Dashboard.