Skip to content
8.1

What to Do If Your Binance Account Is Hacked? Steps to Freeze the Account and Recover It

If your Binance account may have been hacked, work in a fixed order: keep evidence, change passwords from a clean device, freeze the account with the Disable Account feature, clean up API keys and devices, then file a support ticket. 3 tables, 6 steps, risk notes and 7 FAQs.

If your Binance account may have been hacked, do not keep retrying the login in a panic. Open the Binance Official Site or the Official Binance App on a device you are sure is clean, and work through a fixed order: keep evidence, change passwords, freeze the account, clean up authorizations and contact official support.

This article only covers what to do after something looks wrong, not how to prevent it. Prevention has its own articles on this site, such as 2FA, the anti-phishing code and the withdrawal whitelist. BabiaTech is an independent third-party tutorial site, not Binance, and it cannot replace official support in handling any account problem. Every menu and feature below is described as it generally works, so follow whatever the official Binance pages and the app currently show.

The Short Answer: The First Three Things to Do After a Suspected Hack

A: The first three things are to confirm the device is safe, change the login credentials and freeze the account. The order matters: if the phone or computer itself carries malware, a new password typed on that device can be captured by the same malware again.

The first step is to switch to a device you are sure is clean, or to run a virus and system check on the current one. The second step is to log in through an official channel on that clean device, change the password and also change the password of the linked email account. The third step is to use the "Disable Account" self-service feature in the Binance app or web version, which freezes the account as a whole so that an attacker cannot keep logging in, placing orders or withdrawing.

Once those three steps are done, handle API keys, device authorizations and the withdrawal whitelist, and then contact official support. Taking a screenshot or a note at every step is recommended, because it helps with the appeal later.

How to Tell Whether the Account Has Really Been Hacked

A: The evidence of a hack is not a bad feeling but a login, a settings change, an order or a withdrawal that you did not make yourself. Receiving a strange email alone does not mean the account has been hacked.

The table below matches common signals with the right first reaction:

Warning sign Possible cause First reaction
A login or new-device alert for an action you did not take Leaked password, forwarded verification code, controlled device Change the password first, then check device management and login history
An email saying security settings were changed The attacker is already inside the account or the mailbox Freeze the account at once and check whether the mailbox has forwarding rules you did not set
Orders in the account that you never placed Leaked login credentials or API keys Check API management and disable every key
Unknown withdrawals or newly added withdrawal addresses The account is fully controlled Freeze the account, keep the records and contact official support quickly
Only a strange SMS or email, and no unusual account activity A phishing attempt; the account has not been hacked Do not click links, verify with the official tool and strengthen the security settings

If you only received a suspicious email or text message and the account shows no action you did not take, it is usually a phishing attempt and not a hacked account. In that case there is no need to freeze the account, but checking device management and login history and turning on unusual-login alerts is still advisable.

Step 1: Keep the Evidence and Do Not Delete Anything Yet

A: Step 1 is to keep evidence, including screenshots of unusual emails, login alerts, order records and withdrawal records. The more complete the evidence, the more convincing the explanation to official support will be.

The items to keep can be organized as follows:

  1. Unusual emails and text messages, kept in their original form. Do not delete them and do not click the links inside.
  2. Screenshots of the login history, device list, order records and withdrawal records in the Binance account.
  3. If there was a withdrawal, the coin, amount, network, destination address and transaction hash (TxID).
  4. A short timeline of unfamiliar apps recently installed on the phone and unfamiliar links that were clicked.

When saving evidence, do not capture screens that show a full password, verification code or backup key. Screenshots are only for explaining the situation, and they should never be sent to a stranger claiming to be "support".

Step 2: Change the Password and the Email from a Clean Device

A: Step 2 is to log in through the official entry on a device confirmed to be clean, change the password, and change the password of the linked email account as well. The mailbox is the entry point for password recovery, so if the mailbox is compromised, changing only the Binance password will not stop an attacker from resetting the account.

The process has three small parts. First run a virus check on the phone or computer and uninstall any unfamiliar apps installed recently. Then open the Binance Official Site from a bookmark or an official channel, verify the domain and certificate, and log in. Finally change the Binance login password to one that is not reused on any other website, change the email password at the same time, and turn on two-step verification for the mailbox itself.

If login is already impossible, the attacker may have changed the password or the linked details. The official "Forgot password" flow can be tried, but do not submit it many times in a row and do not enter account details on any unfamiliar page. If the reset fails, go straight to Step 5 and contact official support.

Another article on this site explains where to find device management and login history in Binance, and it can be used to double-check after the password change.

Step 3: Freeze the Account with the Disable Account Feature

A: Binance provides an account-level self-service "Disable Account" feature; once it is enabled, login, trading and withdrawals are generally suspended, which helps stop losses quickly when a hack is suspected. This is what the article calls "freezing the account". The feature name and its location follow whatever the app or web version currently shows.

The feature is usually found on a security-related page or an account-activity-related page of the account. The system asks for identity verification during the operation, such as an email code or an authenticator code. After the account is disabled it has not been deleted, and the assets are still recorded in it, but an official verification process is required to enable it again.

A few points to understand beforehand:

  • Disabling the account stops the attacker from continuing to operate; it is not account closure and it does not automatically recover assets that have already been moved.
  • Re-enabling the account after disabling it generally requires official support or a verification process designated by Binance. The exact steps and required materials follow Binance's current instructions.
  • If the attacker has already changed the linked email or the verification method, the self-service feature may be unable to complete verification, and official support should be contacted directly.
  • Binance has not published a uniform processing time, so this article gives no specific timeline. Follow the official page and the replies from support.

Step 4: Check and Clean Up API Keys, Devices and Withdrawal Addresses

A: Step 4 is to remove the "back doors" an attacker may have left, including API keys, authorized devices and unknown addresses in the withdrawal whitelist. Even after the password is changed, API keys that were already created and devices that were already authorized can sometimes remain usable.

Work through the table item by item:

Item to check What to look at What to do if something is wrong
API management Keys you did not create, and whether permissions include withdrawals Delete unknown keys; rebuild the keys you use yourself as well
Device management Unfamiliar device names, login regions and login times Remove unfamiliar devices and log in again on your own devices
Withdrawal whitelist Addresses you never added Delete unknown addresses and keep a screenshot as evidence
Verification methods Whether the 2FA authenticator, phone number or email was changed Bind them again and keep the backup key on paper only
Anti-phishing code Whether the code in official emails matches the one you set Set a completely new string of characters

Details on cleaning up API keys can be found in another article on this site about what to do when a Binance API key leaks. If the account has already been disabled, some pages may not be reachable; these cleanup actions can wait until the account is enabled again, but they must be finished before normal use resumes.

Step 5: Contact Official Support and File a Ticket

A: Step 5 is to file a ticket through Binance's official support channel, explain how the account was hacked and provide the evidence. The support entry should be reached from the Binance website or the official Binance app, and no "support agent" who sends an unsolicited private message should be trusted.

Preparing the materials before filing is recommended. They generally include the registered email or phone number, the approximate time the problem occurred, the screenshots, the withdrawal records with transaction hashes, and a short description of what happened. The exact requirements vary by case and follow the ticket page and the replies from support.

To reach the official channel, open the Binance Official Site and look in the Help Center for "Submit a request" or an entry with a similar name. After submission, the system usually shows a ticket number; write it down and watch the registered mailbox for replies that come from an official domain.

Points to watch during the ticket stage:

  • Communicate only inside the official ticket system, and do not join any group that claims it can "recover assets".
  • Official support never asks for a login password, verification code, backup key or seed phrase; end the conversation at once if such a request appears.
  • Do not file a large number of tickets. Keep one ticket per case and reply inside the same ticket when adding materials.
  • Binance does not promise a fixed processing time or outcome, and this article makes no guarantee about time or results.

Step 6: Hardening the Account After Recovery

A: Once the account is enabled again, every credential and security setting should be configured anew instead of simply restoring the old state. The old password, authenticator and API keys should all be treated as exposed and replaced.

The hardening checklist:

  1. Set a new login password, generated with a password manager so that it is long and not reused.
  2. Bind the 2FA authenticator again and copy the backup key onto paper stored offline.
  3. Set a new anti-phishing code and confirm that later official emails carry this string.
  4. Turn on the withdrawal whitelist and keep only addresses you have verified yourself.
  5. Turn on unusual-login alerts; the matching article on this site describes the steps.
  6. Rebuild only the API keys that are really needed, enable only the required permissions, disable withdrawal permission and set an IP restriction.

For the first period after recovery, checking device management, login history and the assets page once a day is recommended, to make sure nothing new appears.

Handling Different Types of Hack

A: The focus differs by situation, and the key is to work out which link the attacker controlled before deciding what to do first and what to avoid. The table lists common situations:

Situation Do first Do not
Clicked a phishing link and entered the account and password Change the password on a clean device, check devices and login history, set an anti-phishing code Do not keep operating on the original phishing page
A verification code was extracted by a stranger Freeze the account at once, replace the authenticator and contact official support Do not send the new verification code to anyone
API key leaked Delete all API keys and check orders and assets Do not merely switch off permissions while keeping the key
Phone lost or stolen Log in on another device, remove the lost device and freeze the account Do not wait until the assets look abnormal
Mailbox compromised Recover and harden the mailbox first, then deal with the Binance account Do not change only the Binance password and ignore the mailbox

Freezing the Account Compared with Other Measures

A: Freezing the account, changing the password, resetting 2FA and contacting support complement one another, and none of them solves everything alone. The table compares the scope of each measure:

Measure Effect Stops an attacker who is already logged in? Suitable stage
Change the login password Invalidates the old password Not necessarily; an existing session may stay valid The moment something looks wrong
Reset 2FA Replaces the verification method Limited effect on existing sessions After the authenticator is suspected stolen
Disable the account Suspends login, trading and withdrawals as a whole Usually the most direct way to stop losses When a hack is confirmed or highly likely
File a support ticket Official manual review and handling Indirect; depends on the official progress When self-service cannot solve it
Clean up API keys and devices Removes the attacker's access channels Effective against API and device access After the password is changed

Risk Warnings and Security Notes

A: After an account is hacked, the risk of being scammed a second time is often higher than the first, so stay alert. This article is independent third-party tutorial content and does not constitute legal advice, investment advice or a promise of any official outcome.

  • People, groups or websites online that claim they can "recover stolen coins" are mostly secondary scams; never pay any "fee" or "deposit".
  • Official Binance staff never ask for passwords, verification codes, backup keys or seed phrases.
  • For large amounts or clearly criminal conduct, a report can be made to local law enforcement, with all evidence preserved.
  • Crypto asset prices are highly volatile, and trading carries the risk of loss.
  • Users in mainland China should comply with the laws and regulations of their region and judge for themselves the legality of taking part in crypto-related activities.

Frequently Asked Questions (FAQ)

Q: Can coins that were transferred out of a hacked Binance account be recovered? A: It depends on the specific case. On-chain transfers are generally irreversible, and Binance makes no uniform promise about outcomes. Freeze the account at once, keep the transaction hashes, and explain the situation to official support and local law enforcement, following the official replies.

Q: Will the assets be lost after the account is frozen? A: No. Disabling the account only suspends login, trading and withdrawals, and the assets remain recorded in the account. Enabling it again requires an official verification process, and the details follow Binance's current instructions.

Q: Can the account still be frozen if login is no longer possible? A: If the self-service feature cannot be used, file a ticket directly with support through the Help Center on the official website or app, explain that the account was hacked and ask support to help.

Q: How soon does support reply after a ticket is filed? A: Binance has not published a uniform processing time, and reply speed varies with ticket volume and the type of problem. After filing, watch the registered mailbox and add materials inside the same ticket.

Q: How can I tell whether a "support" message really comes from Binance? A: Official support never sends unsolicited private messages asking for passwords, verification codes or backup keys. Binance Verify can check a website address, an email or a social media account, or the conversation can be restarted from the Help Center on the official website.

Q: If I only received a suspicious email and there is no unusual activity, do I need to freeze the account? A: Generally not. A suspicious email is usually a phishing attempt. Do not click the links, check device management and login history, and turn on the anti-phishing code and unusual-login alerts.

Q: Do I need to replace the phone or reinstall the system after recovering the account? A: If the device is suspected of carrying malware, run a virus check first, uninstall unfamiliar apps and, if necessary, back up important data and restore factory settings. On an unclean device, a newly set password can still be captured.

Final Thoughts

When a Binance account may have been hacked, the core of the response is order: confirm the device is clean, change the password, freeze the account with Disable Account, clean up API keys and devices, and finally recover the account through an official ticket. Keeping a record at every step is far more reliable than reconstructing events from memory afterwards.

After everything is handled, it is advisable to reinstall the Official Binance App from an official channel and complete the hardening checklist from Step 6. BabiaTech has no affiliation, agency or commercial partnership with Binance, and the features and pages mentioned here may change as the platform updates, so follow what the Binance website and the official app actually show.