Checklist

  • Assign incident lead
  • Slow or lock targeted channels
  • Pause risky invite paths
  • Capture relevant evidence
  • Post a short member update

Steps

  1. Name one person as incident lead.
  2. Lock or slow the most affected channels.
  3. Pause public invite paths if the attack is ongoing.
  4. Preserve relevant evidence according to your policy.
  5. Post a calm update and avoid speculation.

Raid response works best when the team has already practiced the first few actions. Panic is reduced by small, known moves.

This guide avoids retaliatory tactics and focuses on safety, documentation, and platform-appropriate reporting.

Related guides

More playbooks

Back to guides

Global search

Find news, guides, bots, servers, and tools

Start typing to search the full sample index.