> Discord bot token leaked? Reset it in the Developer Portal, save it in RestoreCord, restart the bot and audit what was touched, without losing verified members.

Source: https://restorecord.fail/bot-token-leaked

# Discord bot token leaked? Reset it without losing your members

A token in a screenshot, a public repo or a compromised staff account gives someone full control of your bot. Fixing it takes minutes, as long as you fix the right thing.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)

Short answer

Reset the token in the Discord Developer Portal, which kills the leaked one instantly. Paste the new token into the bot's credentials in RestoreCord's Dashboard → Bots, save, and restart the bot. Don't delete the bot: that removes every verified member attached to it. Then audit webhooks and the bot's server list.

## What a leaked token gives away

A bot token is the bot's password. Whoever holds it can log in as your bot and do anything its role allows: delete channels, ban members, create webhooks, post in your name. Because your RestoreCord bot usually sits near the top of the role list so it can restore roles, a leaked token is about as dangerous as a hijacked admin. The good news is that it's also the easiest leak to close.

Common ways tokens get out:

* Pasted into a support ticket, DM or staff channel while troubleshooting.
* Committed to a public code repository or shared in a config file.
* Visible in a screenshot or screen share of the Developer Portal.
* Read by a staff member or account that has since turned hostile or been compromised.

## Reset it, then tell RestoreCord

Open your application in the Discord Developer Portal and reset the bot token. The old one stops working the moment you do. Your bot drops offline in the same instant, because RestoreCord is still holding the old token, so move straight on.

In RestoreCord, open **Dashboard → Bots**, pick the bot and paste the new token into its credentials. RestoreCord checks it against Discord as you type, and a green ring means Discord accepted it. Save, then use **Restart Bot** to reconnect. Do this before running any snapshot, pull or role restore.

### Bot Credentials

Sensitive information used to authenticate your bot

Bot Token

••••••••••••••••••••••••••••••••

Client Secret

••••••••••••••••••••••••

Valid Redirect URL

Never send the new token to anyone, including staff helping you clean up. If you need help, describe the problem without the secret.

## Why deleting the bot is the wrong fix

It can feel safer to throw the whole bot away. In RestoreCord, that's the one move that turns a security scare into real loss:

| Option                        | Locks the thief out | Keeps verified members                                 | Reversible                   |
| ----------------------------- | ------------------- | ------------------------------------------------------ | ---------------------------- |
| Reset the token               | Yes, immediately    | Yes                                                    | You can reset again any time |
| Delete the bot in RestoreCord | Yes                 | No, every member and server record attached to it goes | No                           |

Members authorized your bot when they verified. That authorization is what lets RestoreCord pull them back after a disaster, so keeping the bot keeps your safety net.

## Check what the thief touched

1. 1Open Manage Bot Guilds in the bot's advanced settings. It lists every server the bot is in. Leave any you don't recognise.
2. 2Look through each of your servers' webhooks and integrations for anything new, and delete it.
3. 3Read the audit log for actions by the bot account you didn't trigger: deleted channels, bans, role edits.
4. 4If anything was destroyed, restore a snapshot from before the first bad entry, then pull members and restore roles.

If the bot card in RestoreCord says privileged intents are disabled after the restart, turn on Server Members Intent and Message Content Intent in the Developer Portal and restart once more.

## Making the next leak less likely

Keep the Discord application owned by a dedicated account or a Developer Portal team rather than one staff member's personal account. Use the bot only for RestoreCord verification and recovery, so fewer tools and people ever need its token. And when damage does happen, the steps on [recovering a nuked server](https://restorecord.fail/server-nuked) and [handling a rogue admin](https://restorecord.fail/rogue-admin) pick up where this guide stops. The full order lives on the [RestoreCord Recovery home page](https://restorecord.fail/).

## Token reset, start to finish

1. 1  
### Reset the token in Discord  
Open your application in the Discord Developer Portal and reset the bot token. The leaked one dies immediately.
2. 2  
### Save it in RestoreCord  
Paste the new token into the bot's credentials in Dashboard → Bots, wait for Discord to accept it, and save.
3. 3  
### Restart and audit  
Restart the bot, then check Manage Bot Guilds and your server's webhooks for anything the thief left behind.
4. 4  
### Test verification  
Verify with a staff account to confirm the bot is back online and handing out the verified role.
[Open the Bot Management guide](https://restorecord.com/docs/guides/bot-management)

## Leaked token questions

### 

### 

### 

## A new token, the same members

Your RestoreCord bot can change credentials in a minute while every verified member stays exactly where they are.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
