Security

Protect your server with anti-nuke, anti-raid, join gate verification, and fake permissions.

The Security module protects your server against nuking, raids, and unauthorized actions. It includes real-time detection of destructive actions, join verification gates, and a fake permissions system that lets you grant bot-level permissions without giving real Discord permissions.

Quick Reference

Command	Description	Permission	Cooldown
`.antinuke`	Configure anti-nuke protection	Server Owner / AN Admin	3s
`.antiraid`	Configure anti-raid detection	Admin	3s
`.joingate`	Configure join verification gate	Admin	3s
`.fakepermissions`	Manage fake permissions for roles	Admin	3s

Anti-Nuke

The anti-nuke system monitors destructive actions (mass bans, kicks, role deletions, channel deletions, etc.) and automatically punishes the responsible user when thresholds are exceeded. Only the server owner and designated anti-nuke admins can configure it.

Setup

.antinuke enable
.antinuke log #security-log

Subcommands

.antinuke enable                         — Enable anti-nuke protection
.antinuke disable                        — Disable anti-nuke protection
.antinuke settings                       — View current configuration
.antinuke module <type> enable           — Enable a specific module
.antinuke module <type> disable          — Disable a specific module
.antinuke module <type> threshold <n>    — Set the action threshold
.antinuke module <type> punishment <action> — Set the punishment
.antinuke whitelist add <user>           — Whitelist a user (bypass detection)
.antinuke whitelist remove <user>        — Remove a user from the whitelist
.antinuke whitelist list                 — List all whitelisted users
.antinuke admin add <user>              — Add an anti-nuke admin
.antinuke admin remove <user>           — Remove an anti-nuke admin
.antinuke admin list                    — List all anti-nuke admins
.antinuke log <#channel>                — Set the security log channel

Aliases: an

Modules

The anti-nuke system has 8 detection modules:

Module	Detects	Default Threshold
`antiBan`	Mass banning	3
`antiKick`	Mass kicking	3
`antiRole`	Mass role deletion/creation	3
`antiChannel`	Mass channel deletion/creation	3
`antiEmoji`	Mass emoji deletion	3
`antiWebhook`	Mass webhook creation	3
`antiBotAdd`	Unauthorized bot additions	1
`antiVanity`	Vanity URL changes	1

Punishments

Each module can be configured with one of these punishments:

ban — Ban the user
kick — Kick the user
stripstaff — Remove all staff/admin roles from the user
timeout — Timeout the user

Examples:

.antinuke module antiBan enable
.antinuke module antiBan threshold 5
.antinuke module antiBan punishment ban
.antinuke module antiChannel threshold 2
.antinuke whitelist add @TrustedAdmin

Anti-nuke uses Redis atomic counters (INCR + EXPIRE) to track actions in real time. Each action type has its own counter per user, and when the count exceeds the threshold within the time window, the punishment is applied immediately.

Anti-Raid

The anti-raid system detects patterns of malicious join behavior and can automatically respond to raids.

Subcommands

.antiraid massjoin on --threshold <n> --window <seconds> --do <action> [--lock]
.antiraid massjoin off
.antiraid age on --threshold <duration> --do <action>
.antiraid age off
.antiraid avatar on --do <action>
.antiraid avatar off
.antiraid config                         — View current settings
.antiraid state                          — View active raid state
.antiraid clear                          — Clear current raid state

Aliases: ar Permission: Admin

Detection Modes

Mass Join — Triggers when too many users join within a time window.

.antiraid massjoin on --threshold 10 --window 30 --do ban
.antiraid massjoin on --threshold 5 --window 10 --do kick --lock

The --lock flag also locks the server during a detected raid.

Account Age — Blocks new accounts below a minimum age.

.antiraid age on --threshold 7d --do kick
.antiraid age on --threshold 1h --do ban

No Avatar — Blocks accounts without a profile picture (common with bot accounts).

.antiraid avatar on --do kick

Examples:

.antiraid massjoin on --threshold 10 --window 30 --do ban --lock
.antiraid age on --threshold 7d --do kick
.antiraid avatar on --do ban
.antiraid config
.antiraid clear

Join Gate

The join gate requires new members to verify themselves before gaining access to the server. Until they verify, they only see the verification channel.

Setup

.joingate enable
.joingate channel #verify
.joingate role @Verified
.joingate method button

Subcommands

.joingate enable                    — Enable join gate
.joingate disable                   — Disable join gate
.joingate method <button|captcha|none> — Set verification method
.joingate role <@role>              — Set the verified role
.joingate channel <#channel>        — Set the verification channel
.joingate timeout <duration>        — Set how long users have to verify
.joingate attempts <n>              — Set max captcha attempts
.joingate failaction <kick|ban|none> — What happens if they fail
.joingate captcha length <n>        — Set captcha code length
.joingate captcha case              — Toggle case sensitivity for captcha
.joingate setup                     — Auto-setup (creates channel + role)
.joingate reset                     — Reset all join gate settings
.joingate log <#channel>            — Set the verification log channel
.joingate message <text>            — Set the verification message

Aliases: jg, verify, gate Permission: Admin

Verification Methods

Method	How It Works
`button`	New members click a button to verify
`captcha`	New members type a code shown in an image
`none`	No automatic verification (manual only)

Examples:

.joingate enable
.joingate method captcha
.joingate captcha length 6
.joingate captcha case
.joingate timeout 10m
.joingate attempts 3
.joingate failaction kick
.joingate setup

Fake Permissions

Fake permissions let you grant bot-level command permissions to roles without giving them real Discord permissions. For example, you can let a "Trial Mod" role use .ban without giving them the actual Ban Members permission in Discord.

Subcommands

.fakepermissions grant <@role> <permission>
.fakepermissions revoke <@role> <permission>
.fakepermissions clear <@role>
.fakepermissions list [@role]

Aliases: fp, fakeperm, fakeperms Permission: Admin

Available Permission Aliases

You can use short names instead of the full Discord permission names:

Alias	Discord Permission
`ban`	Ban Members
`kick`	Kick Members
`mute`	Moderate Members
`timeout`	Moderate Members
`manage_messages`	Manage Messages
`manage_channels`	Manage Channels
`manage_roles`	Manage Roles

Examples:

.fakepermissions grant @Trial-Mod ban
.fakepermissions grant @Trial-Mod kick
.fakepermissions revoke @Trial-Mod ban
.fakepermissions clear @Trial-Mod
.fakepermissions list @Trial-Mod
.fakepermissions list

Fake permissions only affect Slipz commands. They do not grant real Discord permissions. A user with a fake "Ban Members" permission can use .ban but cannot ban through Discord's native right-click menu.

Fake permissions are cached in Redis with a 5-minute TTL. Changes may take up to 5 minutes to take effect. The cache is checked using a Redis pipeline for performance.

Security

On this page