Discord AntiNuke Selfbot - Protect Your Server

User Guides

Comprehensive guides to help you get the most out of the Discord AntiNuke Selfbot

Configuration Guide

Mobile Setup

Troubleshooting

Hosting Guide

Security Guide

Configuration Guide

The Discord AntiNuke Selfbot configuration is managed through the config/config.yaml file. This guide explains each configuration option in detail and provides recommendations for optimal protection.

Account & Server Settings

Account Configuration

selfbot:
  token: 'YOUR_DISCORD_TOKEN_HERE' # Your account token
  server1_id: '111222333444555666' # First server to protect
  server2_id: '222333444555666777' # Second server to protect (optional)
  owner1_id: '123456789012345678' # Your Discord user ID
  owner2_id: '234567890123456789' # Another owner ID (optional)

yaml

Option	Type	Description
token	String	Your Discord account token. This is required for the selfbot to function.
server1_id	String	ID of the first server you want to protect. Must be a valid Discord server ID.
server2_id	String	Optional second server to protect. You can leave this empty if you only need to protect one server.
owner1_id	String	Your Discord user ID. The selfbot will send alerts to this user when security events occur.
owner2_id	String	Optional second owner ID. You can add an alternative account or a trusted admin here.

Important: Never share your Discord token with anyone or commit it to public repositories. It provides full access to your account!

Protection Settings

Protection Configuration

antinuke_settings:
  punishment: 'ban' # Options: 'ban', 'kick', or 'none'
  auto_recovery: true # Automatically recover channels and roles
  recover_channels: true # Recover deleted channels
  recover_roles: true # Recover deleted roles
  recovery_delay: 1500 # Milliseconds to wait between recoveries
  
  # PROTECTION THRESHOLDS
  ban_limit: 5 # Triggers if someone bans 5+ people quickly
  kick_limit: 5 # Triggers if someone kicks 5+ people quickly
  channel_create_limit: 5 # Triggers if someone creates 5+ channels quickly
  role_create_limit: 5 # Triggers if someone creates 5+ roles quickly
  channel_delete_limit: 5 # Triggers if someone deletes 5+ channels quickly
  role_delete_limit: 5 # Triggers if someone deletes 5+ roles quickly
  channel_update_limit: 5 # Triggers if someone changes 5+ channels quickly
  role_update_limit: 5 # Triggers if someone changes 5+ roles quickly
  member_update_limit: 5 # Triggers if someone changes 5+ members quickly
  unban_limit: 5 # Triggers if someone unbans 5+ people quickly
  
  # TIME WINDOW FOR COUNTING ACTIONS (IN MILLISECONDS)
  # 36000000 = 10 hours, 3600000 = 1 hour, 600000 = 10 minutes
  time_window: 36000000

yaml

The protection settings control how the AntiNuke Selfbot responds to potential threats and malicious actions. You can adjust these settings based on your server's activity level and security needs.

Recommendation: Start with the default limits (5) and adjust them based on your server's normal administrative activity. Busy servers might need higher thresholds.

Whitelist Configuration

whitelisted:
  users: ['123456789012345678', '234567890123456789'] # Trusted admin IDs

yaml

The whitelist contains the Discord user IDs of trusted administrators who should not trigger the AntiNuke system when performing administrative actions.

Security Note: Only add completely trusted users to the whitelist. Anyone on this list can perform administrative actions without triggering protection.

Mobile Setup Guide

This guide will help you set up and run the Discord AntiNuke Selfbot on your Android device using Termux. Please note that mobile hosting is generally not recommended for 24/7 protection due to battery limitations and system restrictions.

Important: Mobile hosting has several limitations including battery drain, thermal issues, and OS-enforced background restrictions that may prevent continuous operation.

Installing Termux

Download Termux

Download Termux from F-Droid (recommended). The Google Play version may be outdated.

Update Packages

Update Termux Packages

pkg update && pkg upgrade -y

bash

Install Required Packages

Install Dependencies

pkg install nodejs git nano -y

bash

Installing the Selfbot

Clone the Repository

Clone Repository

mkdir -p ~/antinuke
cd ~/antinuke
git clone https://github.com/faiz4sure/discord-antinuke-selfbot.git
cd discord-antinuke-selfbot

bash

Install Dependencies

Install NPM Packages

npm install

bash

Configure the Selfbot

Edit the configuration file using nano:

Edit Configuration

nano config/config.yaml

bash

Edit the configuration with your information, then save and exit by pressing Ctrl+O, Enter, then Ctrl+X.

Running in Background with Tmux

To keep the selfbot running even when Termux is closed, use tmux:

Setup Tmux for Background Running

# Install tmux
pkg install tmux -y

# Create a new tmux session
tmux new -s antinuke

# Start the selfbot (inside tmux)
node index.js

# Detach from tmux (keep running in background): press Ctrl+B, then D
# To reattach later:
tmux attach -t antinuke

bash

Preventing Android from Killing the App

Disable battery optimization for Termux in your phone settings
Lock Termux in your recent apps
Add Termux to your phone's "protected apps" list if available
Keep your phone connected to a power source

Tip: Alternatively, consider using a proper VPS (Virtual Private Server) or dedicated hosting service for more reliable 24/7 protection.

Troubleshooting Guide

Encountering issues with the Discord AntiNuke Selfbot? Use this troubleshooting guide to diagnose and resolve common problems.

Common Issues and Solutions

Invalid Token Error

Problem: The selfbot fails to start with an "invalid token" error.

Solution:

Make sure your Discord token is correct and not expired
Check if your Discord account is still active and not locked
Verify that you haven't enabled two-factor authentication recently, which might invalidate the current token

Permission Issues

Problem: The selfbot can't ban/kick users or take other actions.

Solution:

Ensure your account has Administrator permission in the protected servers
Check the role hierarchy - your role must be high enough to take action against other roles
Verify you're not trying to take action against the server owner or users with higher roles

False Positives

Problem: The selfbot is triggering on legitimate administrative actions.

Solution:

Increase the threshold limits in config.yaml
Add trusted administrators to the whitelist
Increase the time_window value to allow more actions over a longer period

Memory Issues

Problem: The selfbot crashes with out-of-memory errors.

Solution:

Ensure your hosting has at least 512MB RAM
Reduce the number of servers being protected simultaneously
Check for memory leaks in custom modifications if you've changed the code
Use a process manager like PM2 to automatically restart after crashes

Rate Limiting

Problem: The selfbot is being rate limited by Discord.

Solution:

Increase the recovery_delay setting to slow down actions
Decrease the protection thresholds to act earlier (before many actions are needed)
Implement gradual recovery rather than bulk operations

Diagnostics Commands

Use these commands to diagnose issues with your selfbot installation:

Diagnostic Commands

# Check Node.js version
node -v

# Check npm version
npm -v

# Verify package installation
npm list

# Check for errors in logs
cat logs/errors.txt

# Monitor real-time logs
tail -f logs/errors.txt

bash

Need More Help? Join our support server for personalized assistance with your specific issue.

Hosting Guide

For the Discord AntiNuke Selfbot to provide effective protection, it needs to run 24/7 without interruption. This guide covers the best hosting options and setup methods.

Recommended Hosting Options

VPS (Virtual Private Server)

Best Option: A VPS provides reliable 24/7 uptime with full control over the environment.

Recommendations:

DigitalOcean ($5/month droplet)
Linode ($5/month plan)
OVH ($3.50/month VPS)
Oracle Cloud (free tier available)

Home Server

Good Option: If you have a computer that runs 24/7, you can host the selfbot there.

Requirements:

24/7 power and internet connection
Process manager like PM2 to handle restarts
At least 512MB RAM available

Free Cloud Hosting

Budget Option: Some cloud services offer free tiers that can run the selfbot.

Options:

Oracle Cloud Free Tier
Google Cloud Platform Free Tier
Heroku (with workarounds to prevent sleep)

Setting Up with PM2 (Recommended)

Process Manager 2 (PM2) is the best way to keep your selfbot running continuously. It handles crashes, system reboots, and provides monitoring.

PM2 Setup Commands

# Install PM2 globally
npm install -g pm2

# Start your application with PM2
pm2 start index.js --name 'antinuke'

# Set PM2 to start on system boot
pm2 startup
pm2 save

# View running processes
pm2 list

# Monitor logs
pm2 logs antinuke

# Restart the application
pm2 restart antinuke

bash

Pro Tip: PM2 offers a web-based monitoring interface. You can enable it with pm2 plus for additional insights into your selfbot's performance.

Security Guide

The Discord AntiNuke Selfbot provides powerful protection for your server, but it's important to follow these security best practices to ensure optimal protection while minimizing risks.

Account Security

Use a Secondary Account

Using selfbots violates Discord's Terms of Service. To minimize risk to your main account, use a dedicated alt account for running the selfbot.

Secure Your Token

Never share your Discord token with anyone or commit it to public repositories. Store it securely and consider using environment variables instead of hardcoding it.

Limit Permissions

Only give your selfbot account the necessary permissions it needs to function. While Administrator permission makes setup easier, consider using more granular permissions if possible.

Optimal Configuration

Careful Whitelisting

Only whitelist users you completely trust. Anyone on the whitelist can perform administrative actions without triggering the protection system.

Fine-tune Thresholds

Adjust protection thresholds based on your server's activity. Lower thresholds provide stronger protection but may cause false positives. Test different settings to find the right balance.

Regular Auditing

Regularly review the selfbot's logs to ensure it's functioning correctly and adjust settings as needed based on any false positives or missed security events.

Important Disclaimer: Using selfbots violates Discord's Terms of Service and may result in account termination. Use this software at your own risk and for educational purposes only.

Advanced Guides

User Guides

Configuration Guide

Mobile Setup

Troubleshooting

Hosting Guide

Security Guide

Configuration Guide

Account & Server Settings

Protection Settings

Whitelist Configuration

Mobile Setup Guide

Installing Termux

Download Termux

Update Packages

Install Required Packages

Installing the Selfbot

Clone the Repository

Install Dependencies

Configure the Selfbot

Running in Background with Tmux

Preventing Android from Killing the App

Troubleshooting Guide

Common Issues and Solutions

Diagnostics Commands

Hosting Guide

Recommended Hosting Options

Setting Up with PM2 (Recommended)

Security Guide

Account Security

Optimal Configuration

Important Disclaimer

Ready to Secure Your Server?