Zippy WallAntiNuke for Discord
Stop compromised mod accounts from nuking your server.
Per-user limits on bans, kicks, channel deletes, role deletes, and bot adds. Designed to catch compromised staff accounts before they wipe your server.
Pro feature — $3.99/mo, 14-day free trial. Includes anti-raid + cross-server raider blocklist.
AntiNuke
AntiNuke works by setting limits on dangerous actions. If a user exceeds any of these limits in the window specified the resulting action will be triggered.
Nuking is when a user (usually a compromised mod account) begins kicking/banning users, deleting channels, and other harmful actions. Zippy Wall has pre-defined criteria in the Pro version which lock botting activity such as deleting multiple channels too quickly.
Seven actions tracked, per user
Each user gets their own rolling-window counter for each action type.
| Action | Default limit | Why this threshold |
|---|---|---|
| Bans | 10 / 60s | Manual mod cleanup rarely hits 10 bans per minute |
| Kicks | 10 / 60s | Same reasoning as bans |
| Channel deletes | 2 / 60s | No legitimate workflow deletes two channels in a minute |
| Channel creates | 5 / 60s | Batch creation during server setup is occasionally legit |
| Role deletes | 2 / 60s | Server-defacement signal — keep this tight |
| Role creates | 5 / 60s | Same shape as channel creates |
| Bot adds | 5 / 60s | Catches malicious-bot injection during a compromise |
Set any limit to 0 to skip that action entirely. Adjust the window from 60 to 3600 seconds per server.
Four response modes
What happens when a user crosses a limit. Start safe, escalate as you tune.
Strip all User Roles
When a user crosses any limit, Zippy Wall removes every role below its own. The user keeps their account but loses all permissions instantly. Reversible — an admin can re-grant in seconds. Best for first-time setup and tuning.
- ✓ No permanent damage
- ✓ Stops the attack instantly
- ✓ Easy to recover from false positives
Kick from server
Removes the user entirely. They can re-join via invite but lose all permissions and roles. Useful when you're confident in your thresholds and want a stronger signal than role-strip.
- ✓ User can re-join
- ✓ Forces attacker to re-auth
- ✓ Cleaner audit trail
Permanent ban
Bans the offender outright. Use only when you're confident in the limits. Recommend running on LOG_ONLY for at least a week first to validate thresholds.
- ✓ Strongest deterrent
- ✓ Attacker can't easily return
- ✓ Best for high-target servers
Alert mods, take no action
Posts to your mod log channel but takes no automated action. Use this for the first 7 days to see what would have tripped before enabling enforcement. Best way to tune without risk.
- ✓ Avoids false positive risk
- ✓ Validates thresholds
- ✓ Best first-week setting
How AntiNuke actually works
One detection mechanic, four response shapes, exemptions for the staff you trust explicitly.
Rolling window per user, per action. Every ban, kick, channel-delete, role-delete, and bot-add increments a counter.
When count-in-window crosses the limit, the response mode fires immediately — strip roles, kick, ban, or log.
Mod-log channel gets a structured embed with the full incident: user, action, count, threshold, response.
What you get
AntiNuke layered with the rest of Zippy Wall's firewall stack.
Set any limit to 0 to skip that action entirely. Want to track bans + role deletes but not channel creates? Done. Each limit tunes separately so you can match your server's actual workflow.
The 60-second window discriminates by rate (events/minute) instead of total count. Real attacks hammer 5–20 actions/minute; legitimate cleanup paces at 0.5–2/minute. The window is tunable (60–3600s).
The whole point is catching compromised admin accounts. Discord's permission system doesn't help here — the attacker already has the permission. AntiNuke watches behavior instead. Add trusted senior staff to the explicit exempt list.
Every nuke trigger posts a structured embed: user, action that tripped, current count vs limit, response taken. Full incident record without leaving Discord.
Anti-raid catches outside attacks (mass joins). AntiNuke catches inside attacks (compromised mods). Both run independently and don't conflict.
STRIP_ROLES is the default response for a reason — easy to undo if you mis-tune. Escalate to KICK or BAN only after you've validated the limits against your real mod activity.
Setup in 30 seconds
Sensible defaults baked in. Tune later if you want.
- Step 1Add Zippy Wall to your server
One-click Discord invite. AntiNuke needs the View Audit Log permission to see mod actions.
- Step 2Click "Quick start" on the dashboard
Enables AntiNuke with recommended defaults: limits set per action above, window 60s, response Strip Roles.
- Step 3Add your senior staff to the exempt list
Trusted admins who do high-volume cleanup work should go in the exempt-users or exempt-roles list, or you'll trip AntiNuke during legitimate post-raid cleanup.
- Step 4 — optional but recommendedRun on LOG_ONLY for a week
Watch the mod-log to see what would have tripped. Tune limits if you see false positives. Switch to STRIP_ROLES when confident.
Common questions
Won't this catch my admins doing legit cleanup?
It might, if they hit the limits. The default 10 bans / 60s is high enough that normal mod work rarely trips it — banning 10 users in a minute requires lookup + click + confirm per action, which paces around 0.5–2 bans/minute. But during heavy post-raid cleanup an admin can plausibly hit 10/minute, which is why you should add senior staff to the exempt-roles list before enabling enforcement.
Why not just trust the Administrator permission?
Because the threat model is the Administrator permission being misused. AntiNuke watches behavior to catch compromised admin accounts — if Administrators were auto-exempt, the feature would do nothing for the case it's designed for. Add trusted admins to the exempt list explicitly so you're signing "I trust this person's account" instead of "I trust anyone with this permission."
What permissions does AntiNuke need?
View Audit Log is required — that's how the bot sees mod actions. The chosen response mode needs the matching permission: STRIP_ROLES needs Manage Roles, KICK needs Kick Members, BAN needs Ban Members. We never ask for Administrator.
My admin got role-stripped — how do I recover?
Re-grant the role manually — it's a normal Discord action. Then add the admin to the exempt list so it doesn't happen again. STRIP_ROLES is the default specifically because it's easy to recover from; if you escalated to BAN and false-positived, you'd have to unban + re-grant, which is more friction.
Ready to harden your server?
14-day free trial. No card required to install. Configurable in 30 seconds.
Add Zippy Wall to Discord