Current problem
Today, if a single staff member's account gets compromised, an attacker can destroy an entire community within seconds. Standard anti-raid tools only stop spam joins. They cannot prevent an attacker from joining with a brand-new alt account, receiving Administrator from the hijacked staff account, inviting a malicious bot, and wiping hundreds of channels and roles before any human can react. Communities currently have no native way to slow down privilege escalation or mass deletions without relying on fragile, self-hosted third-party bots.
Proposed change
Build proactive anti-nuke and privilege escalation guardrails directly into Fluxer's community security settings:
• Privilege Escalation Cool-downs (Account & Server Age Gates): Block accounts younger than a configurable threshold (e.g., under 7 days old) or members who joined the community recently (e.g., within the last 24 hours) from receiving high-risk permissions like Administrator, Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Ban, or Kick.
• Bot Addition Restrictions & Owner Approval: Prevent new accounts or newly joined members from inviting bots, even if they temporarily hold Administrator. Add an optional toggle requiring Server Owner approval before any bot can be added.
• Destructive Action Velocity Limits: Enforce per-minute community rate limits on destructive actions (e.g., max 5 channel deletions, 3 role deletions, 5 bans/kicks, or 3 webhook creations per minute). Automatically strip privileged roles or suspend/ban a bot the instant it crosses the limit.
• Owner & Audit Log Alerts: Send instant alerts to the community owner and a designated moderation log channel whenever a bot is added, a privileged role is granted, or a velocity limit is triggered.
• "Report Mode" (Dry-Run Testing): Allow community owners to enable these protections in a passive Report Mode first so admins can see what would have been flagged based on normal staff activity before turning on active enforcement.
• Soft-Delete / Recovery Window: Add a short recovery window (e.g., 24–48 hours) for deleted channels and roles so a rogue action cannot permanently erase years of community history.
Platform
macOS, Windows, Linux, Web, Android, iOS, API, Self-hosting
Additional information
This design is inspired by the open-source Discord anti-nuke bot Newtype (https://github.com/), which was created after a 24,000-member community lost 204 channels in 11 seconds when a staff account was compromised.
Unlike traditional anti-nuke bots that rely on rigid staff allowlists or only react after mass deletions start, gating permissions by account age and server join time cuts off the attack chain at the role-grant step before a bot can ever be invited. Having this built natively into Fluxer's permission and gateway engine protects both fluxer.com communities and self-hosted instances right out of the box.