Skip to main content
Antinuke is Hedwig’s emergency layer for destructive server actions. It is designed to reduce the blast radius of compromised accounts, rogue bots, and mass changes. The implementation monitors 25 event types, including channel, role, webhook, integration, ban, kick, unban, bot-add, mass-mention, member role, prune, dangerous invite, and scheduled-event actions.

​
Enable it safely

1

Configure logging first

Run /logging setup and /logging enable so staff can see what antinuke is reacting to.
2

Review the trust boundary

Use /whitelist and /extraowner manage to inspect who can bypass protection. Only the server owner or an extra owner can enable, disable, reset, or manage the antinuke trust boundary. Keep both lists intentionally small.
3

Enable and verify

Run /antinuke enable, then /antinuke status to confirm the active modules. Enabling also prepares the Hedwig's Antinuke role used by the protection system; follow the response’s hierarchy instruction.

​
Commands

Do not add an entire staff role to the antinuke allowlist without reviewing who has that role. A compromised trusted account can bypass the protection you intended to add. This is not a replacement for Discord audit-log review or a least-privilege staff role design.

​
Incident response

  1. Check /antinuke status.
  2. Review the latest event logs.
  3. Remove suspicious allowlist or extra-owner entries.
  4. Pause automation that may be contributing to the incident.
  5. Use /antinuke disable only when you understand the trade-off and are actively investigating.