Skip to main content
A Venon Security guide

How do you protect a Discord server from a raid?

Three layers: the entry gate, threat detection and logs. Below are the exact setting names, the rollout order and a final test.

8

Configuration steps

5

Final tests

4

Errors solved

~9 min

Reading time

The answer

The short answer

To protect a Discord server from a raid, set up three layers at once: the entry gate (verification plus a minimum account age), detection thresholds for join waves and spam, and a log channel that records how the incident unfolded. AntiRaid and RaidWatch run in monitor-only mode: they report threats and prepare a response plan rather than apply penalties on their own. In Venon Security you configure these layers on the Community → Onboarding Center → Verification, Security → Raid protection and Moderation → Moderation log screens. Below are the rollout steps and a way to check the configuration.

The content is checked against the bot's configuration — last verified: 2026-11-06.

Context

What the problem is

A raid combines several vectors at once: a sudden wave of freshly created accounts, spam across many channels, mass mentions and phishing links. The moderation team gets dozens of events a minute, and every manual decision costs a few seconds. That is why the defence has to be set up before the attack starts — during one you only get to limit the losses.

Without an extra bot

What you can do with Discord alone

Before you reach for a bot, get everything out of what Discord gives you out of the box. Some problems are solved here, and the rest of the configuration will run more steadily.
  1. 1

    Raise Discord's native verification level (Server settings → Moderation) — Discord will then require a confirmed email address or phone number.

  2. 2

    Take the Send Messages and Embed Links permissions away from @everyone on the channels where new people do not need to write.

  3. 3

    Leave one public entry channel with the rules, and hide the rest from anyone without the access role.

  4. 4

    Agree in writing who declares a lockdown, who clears the channels and who writes the announcement for the community.

Venon Security

What Venon Security adds

Only the things Discord's native tools do not handle, or handle without history and automation.
  • AntiRaid and RaidWatch measure join and message rates. They run in monitor-only mode: they alert and prepare a response plan, but do not mute, kick, ban or start a lockdown themselves.

  • Verify requires members to pass the entry gate, while AntiFake assesses account risk (age, name pattern) and records a signal for review. AntiFake does not quarantine accounts on its own in monitor-only mode.

  • AutoMod and LinkShield remove spam and phishing during the wave, and the log categories record the author, the content and the action taken for later analysis.

Configuration

Configuration step by step

Every step says exactly where to perform it and which fields to set. The field names are the same as in the panel, so you can copy them one to one.

0 of 8 steps

0%
  1. Check the bot's permissions and role position

    Discord server settings → Roles

    This is the one step most later configurations fall apart on. The bot will not grant a role or remove anyone whose role sits above its own — no matter what you set in the panel.

    • Drag the Venon Security role above every role it is meant to manage (Verified, Muted and so on).
    • Leave the bot these permissions: Manage Roles, Manage Messages, Manage Channels, Kick Members, Ban Members, Moderate Members.
    • Do not grant Administrator — the full set above is enough, and it limits the damage if the bot is ever compromised.
  2. Enable the entry gate and verification

    Panel → Community → Onboarding Center → Verification

    The gate cuts off the cheapest form of attack — accounts created in bulk a minute before the raid. Start with the simplest verification type; switch to a captcha only once you see real bot traffic.

    • Verification active: on.
    • Verification type: Button (the least friction), or Captcha (image) if bots are already getting through.
    • Verification channel and Role after verification: point to the entry channel and the access role.
    • Min. account age (days): 3–7 days filters out most accounts created for the attack.
    • Use the Automatic setup button if you have no channel and role yet, then Publish the panel.
  3. Set the AntiRaid thresholds

    Panel → Security → Raid protection/venonsec-panel

    The thresholds depend on the size of your server. Set them slightly above your normal peak-hour traffic, so a promotion does not trigger a lockdown.

    • Join wave (joins/min): small server 5, medium 10, large 20–30.
    • Message spam (msg/5s): 5 is a safe starting point.
    • Slowmode (seconds) and Slowmode duration (seconds): the first, least invasive response.
    • Propose a full lockdown: tick it only after watching the thresholds for a few days — you still approve it in Venom Shield.
  4. Enable RaidWatch and an alert channel

    Panel → Security → Raid protection → Monitoring and alerts

    RaidWatch is the observation layer: it measures the event rate in short windows and writes to the staff channel. That way you see the attack even when nobody happens to be watching the chat.

    • RaidWatch active: on; Alert channel (ID): a private staff channel.
    • Window thresholds: Messages / min, Joins / 5 min, Fast joins (count), Fast join window (s).
    • Planned responses to an attack: start with Mute on spam; tick Kick / Ban / Lockdown on a raid deliberately — Venom Shield carries out the lockdown after approval, while kicks and bans from the plan are done by a moderator.
    • The Detected events (7 days) and Recent alerts cards show whether the thresholds are realistic.
  5. Enable scoring for new accounts

    Panel → Security → Accounts and risk

    AntiFake scores the risk of every join rather than applying one rigid rule. In monitor-only mode it records signals, while a moderator decides whether to restrict an account's access.

    • AntiFake enabled and Raid detection: on.
    • Quarantine role (ID): a role with no channel access — safer than an immediate ban.
    • Log channel (ID): where the risk reports go.
    • The New account risk distribution and Join trend cards show whether the threshold is catching ordinary members.
  6. Turn content protection on for the duration of the wave

    Panel → Security → Content protection

    A raid almost always carries spam and links. AutoMod together with LinkShield takes that traffic off automatically, so the moderators handle decisions rather than deleting messages.

    • AutoMod active, Anti-spam and Mention limit: on.
    • Max. mentions in a message: 4–5 is enough for a normal conversation.
    • LinkShield active and Block Discord invites: on.
    • Response to a violation: Delete the message and Log to the moderation log channel.
  7. Set up the log channels

    Panel → Moderation → Moderation log → Log channels

    Without logs, all that is left after an incident is screenshots and memory. The Automatic setup button creates the full set of channels in one category and sets the permissions right away.

    • Click Automatic setup, then enable at least these categories: Moderation, Deleted messages, Roles, Invites.
    • Viewer role: the staff role — log channels should be invisible to @everyone.
  8. Make a backup and rehearse the procedure

    Panel → Server → Backups/backup create

    A backup saves the roles, the channels and the module configuration. It is the last line of defence if an attacker manages to delete something — and at the same time a point of reference after the incident.

    • Create a copy with a description, for example before a promotional campaign.
    • Rehearse emergency mode with the team: Panel → Security → Emergency mode is manual-first, meaning a lockdown and recovery both require human approval.
    • Set an Emergency notification channel, so the staff receive alerts even while the server is locked down.

The steps you tick are saved in your browser — you can come back and finish later.

Verification

How to check the configuration worked

A green switch in the panel is not proof. Go through the tests below — ideally on a second, ordinary account with no roles.
  1. 1

    Join the server on a second, ordinary account with no roles — you should see only the verification channel and the rules.

  2. 2

    Go through verification: the access role appears within seconds, and the Roles log category carries an entry about it being granted.

  3. 3

    On a test channel send 6 short messages in 5 seconds — AutoMod should remove them and leave an entry in the moderation logs.

  4. 4

    Go back to Panel → Security → Raid protection: after the test the Detected events (7 days) card shows a non-zero counter.

  5. 5

    Run /venonsec-panel and check that every shield reports an active state.

Diagnostics

When something does not work

The symptom, the cause and a specific fix. Start from the symptom you see — the cause is usually simpler than it seems.

The bot does not grant the role after verification.

Cause
The Venon Security role sits below the granted role in the role list, or the bot lacks the Manage Roles permission.
Fix
Server settings → Roles: drag the bot's role above the target role and check its permissions. Then repeat verification on a test account.

AntiRaid raises an alert during an ordinary influx of people.

Cause
The Join wave (joins/min) threshold is lower than the server's real traffic after an announcement or a stream.
Fix
Check the Detected events (7 days) card, raise the threshold above your usual peak and untick Propose a full lockdown until the thresholds settle.

Nothing shows up in the log channel.

Cause
The log category is switched off, or it has no channel assigned.
Fix
Panel → Moderation → Moderation log: use Automatic setup or assign a channel to the Moderation category by hand, and check that the category switch is on.

New accounts write on ordinary channels despite verification.

Cause
The @everyone role still has Send Messages on those channels — Venon does not change permission overrides it did not create itself.
Fix
On every channel except the entry one, take View Channel or Send Messages away from @everyone and grant them to the access role.

Honestly

What this configuration does not solve

The boundaries matter as much as the capabilities. If you are counting on something from this list, you need a different solution — or simply a person.
  • Verification will not tell a determined human from a bot — it raises the cost of entry, but it does not eliminate an attack run by hand.

  • Venon works at the level of Discord's API. It will not stop an attack on Discord's own infrastructure and will not protect members' accounts from being compromised elsewhere.

  • The bot will not automatically recreate channels deleted by an attacker. Restoring channels from a backup is off by default, because it is a risky operation and needs a deliberate decision.

  • No configuration helps if the attacker takes over an account with the Administrator permission. Require 2FA for administrative roles in the server settings.

  • Venon does not moderate private messages between members — Discord gives bots no such access.

FAQ

FAQ – common questions

Is AutoMod alone enough against a raid?+

No. AutoMod works on message content, and a raid starts with a wave of joins. Without an entry gate and AntiRaid thresholds the bots get in and spread across the channels before the first content filter reacts.

When should you lock the server down?+

When the rate of new accounts and spam exceeds what manual moderation can handle, or when you see coordinated messages from many accounts at once. AntiRaid and RaidWatch prepare a response plan. Venom Shield carries out a lockdown after an administrator approves it; crossing an AntiRaid threshold alone does not start one.

Which AntiRaid thresholds suit a small server?+

For a server of a few hundred people, 5 joins per minute and 5 messages per 5 seconds can be an initial observation threshold, with a slowmode plan. The thresholds alone do not enable slowmode. After a week check the Detected events card and adjust them to your server's normal traffic.

Will defensive settings slow ordinary members down?+

If the thresholds match your real traffic, an average member will not notice them beyond a one-off verification. The problem appears when thresholds are copied from a large server onto a small one — which is why it pays to watch the logs for a few days.

Ready?

Set this up in your own Venon Security panel

Every screen mentioned in the guide is in the web panel. You save the configuration by hand and see its state before anything takes effect on the server.