Telegram anti raid setup for raid mode, lockdown, and recovery

You need to be the group owner or an admin who can manage bot permissions and group safety settings.

VibeGuard anti-raid setup works best after the bot has been added to the group and promoted with the permissions your setup needs. Deleting raid spam requires delete-message rights. Muting, banning, or kicking attackers requires member restriction rights. Join request handling requires the relevant approval permissions. Invite-link actions require the proper Telegram admin rights.

You do not need to turn on aggressive enforcement right away. The safest first setup is to open Security Center, choose an anti-raid profile, run it in audit mode, and review what VibeGuard would catch.

Open Security Center from Telegram to review the group’s current safety status.

Check the active group before changing settings. VibeGuard is group-scoped, so each Telegram group keeps its own anti-raid settings, moderation state, incidents, join queues, profiles, recaps, AI usage, and Mini App context.

In Security Center, start with the anti-raid or safety setup area. Look for enabled features, missing permissions, audit mode, rule status, join queue status, and incident history.

Audit mode shows what VibeGuard would flag before the bot deletes messages, restricts members, pauses approvals, or changes chat behavior.

Use audit mode for the first version of your Telegram anti raid setup. Watch for raid signals such as sudden join bursts, repeated first messages, invite-link concentration, bot waves, channel-sender abuse, copied spam, suspicious newcomer timing, and manual admin raid alerts.

Let the group run with audit mode long enough to see real examples. If normal member behavior gets flagged too often, loosen the rule before enforcement.

A Telegram raid can show up in several ways, so your setup should watch more than one signal.

Start with join velocity, invite-link concentration, newcomer first-message bursts, copied messages, repeated scam links, channel-sender abuse, and bot-like behavior. High-risk public groups may also want stricter newcomer rules around posting speed, link behavior, and verification.

Do not treat every new member spike as an attack. Announcements, launches, creator posts, and marketplace events can create normal join bursts. Use Security Center review to separate real risk from healthy growth.

VibeGuard anti-raid protection should be easy for admins to understand during pressure. Use clear states.

Watch means VibeGuard is seeing signals and recording evidence, but not taking aggressive action.

Guard means stricter newcomer checks, closer first-message review, and stronger routing to admin review.

Lockdown is for active incidents. Depending on your permissions and settings, VibeGuard can help pause approvals, limit posting, delete high-confidence spam, challenge newcomers, revoke risky invite links, or summon moderators.

Recovery helps return the group to normal. Review what happened, roll back temporary restrictions where possible, and tune rules before the next attack.

Anti-raid actions should be explicit. Choose what VibeGuard is allowed to do during each state.

For a cautious setup, keep actions audit-only and notify admins. For a stronger setup, allow case creation, join queue review, newcomer challenges, spam deletion, temporary mutes, or approval pauses. For a high-risk public group, admins may allow stricter lockdown behavior after testing.

VibeGuard can only perform actions that your admins allow and that Telegram permissions support. If an action fails, check Security Center diagnostics before assuming the rule is broken.

After a raid or suspected raid, open the incident timeline.

Review which signals fired, which actions were taken, which members or messages were affected, what failed because of missing permissions, and whether any false positives need correction. Serious decisions can connect to cases or appeals where relevant.

When the quiet window passes or admins decide the incident is over, move the group back toward normal. Restore temporary restrictions where possible, note what worked, and update the anti-raid setup for next time.

Troubleshooting:

Problem: VibeGuard sees raid signals but does not take action. Fix: Check whether the rule is still in audit mode and whether enforcement is enabled for that raid state.

Problem: Lockdown cannot restrict members. Fix: Make sure VibeGuard has member restriction rights in Telegram.

Problem: Invite-link actions are failing. Fix: Confirm the bot has the proper invite-link permissions and that the link can be managed by the bot.

Problem: Normal launch traffic is being flagged as a raid. Fix: Lower sensitivity, keep the setup in Watch or audit mode, and review invite-link and first-message patterns before enforcement.

Problem: Admins are not sure what happened during a raid. Fix: Open the Security Center incident timeline and review signals, actions, skipped actions, cases, and recovery notes.