docs

antinuke

stop rogue staff and compromised accounts before they wreck your server.

antinuke watches the audit log for destructive actions. when one person goes over a limit inside a time window, rina punishes them immediately and undoes the damage: deleted channels and roles are recreated and dangerous role grants are reverted.

enable it

,antinuke enable

the first time you enable it, rina turns on the recommended rules. only the server owner and antinuke admins can change antinuke settings.

rules

each rule has a threshold (actions allowed) and a window (seconds).

,antinuke channeldelete on 3 10 ,antinuke ban on 5 60 ,antinuke webhook off
rulewatches
ban / kick / prunemass bans, kicks and member prunes
channelcreate / channeldelete / channelupdatechannel spam, deletes and permission edits
rolecreate / roledelete / roleupdaterole spam, deletes and permission edits
giveroleroles with dangerous permissions being granted
webhookwebhook creation (used for spam raids)
emojiemoji deletion
botaddunapproved bots being added
vanitythe vanity url being changed
guildupdateserver name, icon and settings changes
massmention@everyone / @here spam

punishment

,antinuke punishment ban

options: ban, kick, strip (removes dangerous roles), timeout or jail.

who is trusted

  • server owner: always trusted
  • antinuke admins: ,antinuke admin @user (owner only). they can manage antinuke and bypass it
  • whitelist: ,antinuke whitelist @user lets a user or bot bypass antinuke without managing it

logs

,antinuke logs #security

every trigger posts a container with the executor, the trigger, the punishment and how many actions were reverted. buttons let the owner or an antinuke admin unban the executor in one click, jump to the antinuke settings or open their profile. the server owner also gets a dm.

tips

  • keep rina's role at the top of the role list or it can't punish people above it
  • don't whitelist bots you don't control. a compromised bot is a common nuke vector
  • pair antinuke with the join gate and fake permissions so staff never need real dangerous permissions