Crypto Discord server hacked? Recover it in the right order
When a mod account is phished during a mint, the attacker usually posts a fake claim link, deletes channels and bans staff within minutes. Recovery works if you do it as a sequence: contain, rebuild, bring holders back, then give their roles back.
Short answer
First lock the attacker out by securing the owner account, removing unknown admin roles, webhooks and integrations, and rotating bot tokens. Then restore a RestoreCord snapshot taken before the first malicious change, pull verified members back in, and run the role restore within 7 days.
Secure owner, revoke access, rotate tokens
Channels, roles, permissions, messages
Prior-authorized members only
Re-assign saved roles to members who returned
Staff first, then the community
Step one is containment, not restoring
A restore into a server the attacker can still reach is a restore they can undo, and it wipes the evidence of what happened. Spend the first minutes cutting off access.
- Secure the owner account from a trusted device: new password, check MFA, end unknown sessions, secure the linked email.
- Remove admin roles, integrations, applications and webhooks you don't recognise.
- Rotate every bot token and API key that could be exposed. Never paste replacements into chat.
- Warn holders on your official channels that any link posted during the incident is not real.
- Note UTC times and screenshot the audit log before you start rebuilding.
Scam posts from a hijacked admin look official. Tell your community clearly that you will never ask anyone to connect a wallet from a Discord message, and repeat it after you reopen.
Pick the right recovery path
| What happened | Where to start |
|---|---|
| Channels and roles were wiped, the server still exists | Contain, then restore a snapshot over the existing server |
| The owner account was lost | Recover it through Discord's official support first; restore nothing until then |
| The server was deleted | Create a new server, add your bot, restore the snapshot into it, then pull members |
| Only members were kicked or banned | No restore needed: unban, then pull verified members back |
Restore the structure
Choose the snapshot taken before the first malicious change, which is not always the newest one. The backup previewer lets you browse its channels and messages before you commit. Put your bot's role above every role it needs to create, confirm the target server, and only clear the destination if you mean to rebuild from scratch.
Bring verified holders back
Snapshots hold your structure, not your members. Members come back through a pull: everyone who verified through RestoreCord before the incident is eligible, and RestoreCord adds no cooldown between pulls on any plan. Discord can still refuse individual accounts, so count successes and failures separately instead of promising the old member count.
Give holder and whitelist roles back
A restore recreates roles with new IDs. RestoreCord maps every member's saved roles onto the new ones and keeps that mapping for 7 days, shown as a pending role restore in the dashboard. Pull members first, because Discord can only assign a role to someone who is in the server, then run the role restore with a bot that has Manage Roles.
412 members have roles waiting to be restored · 968 role assignments · Expires in 6d 21h
Roles are recreated with new IDs; each member's saved roles are re-mapped and queued for 7 days.
“Pending Role Restore” shows on the dashboard with member and assignment counts.
Roles can only be assigned to members already in the server.
Runs in the background at Discord-safe rates; cancel any time, assigned roles are kept.
Before the next mint
| Plan | Backups kept | Messages per backup | Scheduled backups |
|---|---|---|---|
| Free | 1 | 50 | No |
| Premium | 5 | 200 | No |
| Business | 30 | 500 | Yes |
| Enterprise | 50 | 2,000 | Yes |
Give moderators their own access through sub-users on Premium and above instead of sharing the owner login, and send verification and security events to a private webhook channel so you notice changes early. Farmers often arrive right after an incident, so read how to keep airdrops for real members, check the crypto price guide for scheduled backups, or go back to the RestoreCord Crypto home.
Before you reopen the server
Work through this list, then reopen in stages: staff, a small holder group, then everyone.
Owner and admins on MFA
Unknown sessions ended and the linked email secured.
Secrets rotated
Bot tokens, API keys and webhook URLs replaced.
Permissions reviewed
Private channels are private again and no stray admin roles remain.
Roles restored
The role restore finished and skipped roles were assigned by hand.
Verification tested
A test account passed captcha and the alt and VPN checks end to end.
Fresh snapshot taken
A new backup of the cleaned-up server, ready for next time.
Hacked crypto server questions
Take the snapshot before you need it
Back up your crypto server today so a phished mod account is a bad hour, not the end of the project.