Skip to main content
Updates
UpdatesReleaseSecurity

AlphaCloud v1.10.4: Anti-Nuke Now Also Guards Webhooks and Your Bots

Two gaps closed in Anti-Nuke: webhooks can be deleted the moment they appear, and only the server owner may kick or ban bots. Plus fixes for Automations, Logging, Starboard and Tickets.

Published on by AlphaCloud2 min read

v1.10.4 came out the same day as v1.10.3 and is small on purpose. It closes two ways around Anti-Nuke that matter when a server is actually under attack.

Webhooks are deleted the moment they appear

A nuke bot does not need to stay on your server to do damage. It creates a webhook, gets removed, and keeps spamming through that webhook. Removing the bot does not stop that.

Anti-Nuke now has two new switches: "Delete webhooks from bots right away" and "Delete webhooks from members right away". A new webhook is gone the moment it is created. The whitelist and the server owner are exempt, so put a bot on the whitelist if it needs webhooks for its normal work. Both switches are off by default, because many servers use webhooks on purpose.

Only the owner may kick or ban bots

The other new switch is "Only the server owner may kick or ban bots". An attacker often removes the protection first, and the protection is a bot. With this switch on, anyone else who kicks or bans a bot is stopped as an offender right away, also when they use /kick or /ban, and a banned bot is unbanned.

A bot that was kicked cannot add itself again, only a person can. So the incident message and the DM to the owner contain the bot's invite link, ready to click. This switch is off by default too. The Anti-Nuke documentation explains all of it.

One change you should know about

Kicks and bans through /kick and /ban now count for the moderator who used them, exactly like kicks and bans by hand. Before, a compromised moderator account could get around the mass ban detection by going through the bot. The other side of this: a moderator who bans many accounts in a short time through /ban, for example during a raid, can trigger the detection. Put the moderators you trust on the Anti-Nuke whitelist.

Fixes

  • Automations and Embed Creator: an embed that an automation still sends can no longer be deleted, the panel names the automation. Automations whose embed was already gone are switched off instead of running into nothing every day
  • Logging and Moderation: a log channel deleted on Discord no longer blocks saving the module, it is simply cleared
  • Starboard: servers whose Premium ended could not save Starboard anymore. The panel now shows and saves the values of the current plan
  • Absences: the absence list showed the German word "bis" in every language. It is now translated, and dates follow the server language
  • Panel: saving several entries at once, such as ticket categories, no longer fails with "could not be checked against the server"

If you run a public server, take two minutes for the new switches in the panel. If you want the background first, we wrote what Anti-Nuke does and what it cannot do.

More articles