Anti-Raid

Anti-Raid helps protect your Discord server from mass-join attacks and suspicious new accounts.

It works alongside Automod but focuses on members joining the server rather than messages already sent in chat.

🛡️ What Anti-Raid detects

Anti-Raid can detect join bursts.

A join burst happens when too many members join within a short time window.

For example:

If 10 members join within 10 seconds, trigger the raid response.

You can configure both the threshold and the time window.

🚨 Raid responses

When a raid is detected, YAWBDB can apply one of several responses.

👢 Kick

Kick recently joined members involved in the burst.

🔨 Ban

Ban recently joined members involved in the burst.

🔒 Lockdown only

Raise the server verification level without removing members.

This is useful when you want to slow down the raid but avoid automatically kicking or banning users.

🔒 Lockdown mode

During lockdown, YAWBDB raises the server verification level to make it harder for new or suspicious accounts to interact.

Lockdown can lift automatically after a configured duration, or remain active until staff manually handles the situation depending on your setup.

⏳ Minimum account age filter

Anti-Raid can also enforce a minimum account age.

If a newly joined account is younger than the configured age, the bot can remove it immediately and alert staff.

This is useful against freshly created spam or raid accounts.

🚨 Alerts

You can configure an alert channel where YAWBDB posts raid or account-age events.

You can also configure a role to ping when alerts happen.

This helps staff react quickly during a raid.

🔗 Anti-Raid and Auto Join Role

Anti-Raid runs before Auto Join Role.

If a new member is kicked or banned by Anti-Raid, YAWBDB avoids trying to assign them an auto-join role afterward.

🔗 Anti-Raid and Appeals

Anti-Raid actions can be recorded in the sanction history.

Depending on the action and configuration, appeals may be created for bans. However, servers may choose not to DM appeal links to obvious raid accounts to avoid rate limits or spam.

👍 Recommended setup

For a small or medium server:

1. Configure an alert channel.
2. Set a conservative join threshold.
3. Start with lockdown-only or kick before using ban.
4. Set a reasonable minimum account age if your server is often targeted.
5. Review alerts after real events and adjust thresholds.

💡 Best practices

• Avoid thresholds that are too low for large communities.
• Use lockdown-only if you are worried about false positives.
• Ping a staff role for important alerts.
• Review Anti-Raid sanctions after large events or public promotions.
• Remember that legitimate member spikes can happen after announcements, streams, or invites.