AntiNuke

AntiNuke watches what people with power are doing and steps in when the numbers stop looking human. If a compromised account bans forty members, AntiNuke punishes the attacker and unbans them.

It is on by default with a threshold of three actions per module, so a fresh server is already protected.

How it decides

Someone has to hit a module's threshold within the detection window. The default window is ten seconds and the default threshold is three actions. Three bans in ten seconds is not a moderator doing their job.

After the punishment, bore keeps quietly undoing that user's destructive actions for two minutes, in case they had helpers or a second account moving at the same time.

The window is yours to change:

,antinuke window 30

Anything from 5 to 60 seconds. A longer window catches a slower attacker. A shorter one almost never false-triggers.

Punishments

Every module takes one of four punishments:

stripstaff is the safer everyday choice: the attacker loses power but stays in the server, so you can investigate. ban is what you want when the account should not come back.

Turning it on and off

,antinuke disable

Pauses everything without forgetting your settings.

,antinuke enable

Turns it back on. There is no per-module on/off for the whole system: individual modules are switched in AntiNuke Modules.

Seeing your setup

,antinuke settings

Alias: configuration. One embed with everything: whether the system is live, which modules are on, each module's threshold and punishment, the window, your admins, your whitelist, how many permissions you watch, and where alerts go.

,antinuke list

Just the enabled modules and their punishments, for a quick read.

Where alerts go

,antinuke logs #mod-logs

Every trigger posts there: who did it, which module, how many actions, what the punishment was, and how many actions bore reverted.

,antinuke logs off

Sends alerts to the server owner's direct messages instead.

Trusting someone with these settings

,antinuke admin @member

Owner only. That member can now change AntiNuke settings, including turning protection off. Run the command again to take it back.

,antinuke admins

Lists them. Bots cannot be made admins.

Whitelisting

A whitelisted member can do destructive things without tripping anything, and a whitelisted bot can be invited without triggering the bot module.

,antinuke whitelist @mod
,antinuke unwhitelist @mod
,antinuke whitelists

Aliases: wl and unwl.

What bore can undo

That table is the argument for stripstaff over kick: a kick is unfixable, a reverted ban list is not.

Next

• AntiNuke Modules for the individual watchers and their commands.
• Watched Permissions for catching power being handed out.
• AntiRaid for join floods, which is a different problem.