Skip to main content

​
Overview

AntiNuke is Flare’s most critical security module. It actively monitors Discord’s audit logs for suspicious, rapid administrative actions—such as mass-banning members, deleting channels, or creating malicious webhooks. When an attack is detected, Flare instantly revokes the attacker’s permissions, issues a punishment (like a ban), and attempts to quarantine the damage.

​
Why should I use it?

Even trusted administrators can have their accounts compromised by phishing links. Without AntiNuke, a compromised admin account can delete years of server history in seconds.

​
Requirements

Crucial Requirement: Flare MUST have the Administrator permission and its role must be placed at the highest possible position in the role hierarchy. Flare cannot punish users who have a higher role than it.

​
Configuration

Setting up AntiNuke requires defining the threshold (how many actions trigger the nuke) and the punishment.
  1. Go to Modules > Anti Nuke.
  2. Toggle the module On.
  3. Under Events, check the actions you want to monitor (Mass Ban, Mass Kick, Channel Deletion, etc.).
  4. Set the Thresholds (e.g., 3 bans per 10 seconds).
  5. Select the Punishment from the dropdown (Ban, Kick, Remove Roles).

​
Events Monitored

Flare’s AntiNuke currently tracks the following vectors:

​
Whitelisting

Some bots (like backup bots or levelling bots) might trigger AntiNuke when doing routine tasks. You must whitelist them.

​
Troubleshooting

Check the audit logs. If the attacker was the Server Owner, Flare cannot take action against them (Discord API restriction). If it was an admin, check if Flare’s role is positioned above the attacker’s role.
Your thresholds might be too low. If your mods regularly ban 3 people in 10 seconds during raids, you should increase the threshold to 5 or 10.