Protecting your server against raids

A raid is often dozens of accounts joining within seconds to flood your channels. Sometimes it’s worse: a compromised staff account deleting channels or banning everyone. Spider protects you from both with three complementary pages in the Protection category.

Layer 1: filter at the door

With Captchas, every new member solves a personal puzzle in a Discord Activity before accessing the server. The “Pending” role only sees the verification channel; the “Verified member” role sees the rest. Automated accounts stay stuck at the door.

Enlarge

Captcha verification for new membersOriginal image

Layer 2: react to bursts

Anti-raid watches mass joins and sensitive actions: channel and role creation or deletion, webhooks, bot additions, kicks and bans in a row. A classic rule: 10 joins in 15 seconds. When it triggers, Spider can sanction, remove dangerous roles, pause invites and lock channels for a chosen duration.

• One incident per burst: all actions from the same author within the window form one incident. The sanction is applied once and the notification is updated instead of repeated.
• Restoration: Spider can recreate deleted categories and channels with their permissions (but not their messages).
• Malicious bots: if the author is a bot, Spider first strips its role permissions before sanctioning it.

Layer 3: monitor

Radar counts every security signal over 24 hours or 7 days and shows a decision log. That’s where you see that a spike happened last night, and what Spider did about it.