Is Bitget Safe?
Essential Reading After the September Security Incident
Withdrawals Fully Restored
On September 24, 2026, unauthorized transfers occurred in certain Bitget hot wallets and warm wallets. Based on official records, this article outlines six verified facts to help you assess platform security independently.
——It has been verified that cold wallets were unaffected, user balances suffered no losses, and the financial impact was covered by ProtectionFund, with an amount exceeding the confirmed impact; withdrawals were fully restored on October 2, 2026.
——It has been verified that cold wallets were unaffected, user balances suffered no losses, and the financial impact was covered by ProtectionFund, with an amount exceeding the confirmed impact; withdrawals were fully restored on October 2, 2026.
Six Security Safeguards
Six Security Safeguards
These six mechanisms do not depend on investigation results—they are structural safeguards that existed before, during, and after the incident
Three-Layer Wallet Segregation Architecture, Cold Wallets Unaffected
This incident affected only certain hot wallet and warm wallet layers. Cold wallets, which hold the largest share of platform assets, were never accessed, and private keys were not compromised.
Fund Security Protection
$314M+ User Protection Fund
Holding more than 3705 BTC. The financial impact of this platform-level incident falls within the fund's coverage—user account balances suffered no losses.
Fund Security Protection
Proof of Reserves (PoR): 131% Overall Reserve Ratio
Proof of Reserves, self-published monthly through a cryptographic Merkle Tree, covers 19 assets. This incident did not affect Bitget's underlying reserves—all covered assets maintain reserve ratios above 100%.
Fund Security Protection
Containment Speed and Independent Review
The reconciliation system detected anomalies within 34 minutes of the first unauthorized transfer and initiated the highest-level emergency response within 9 minutes of detection. Independent investigations by Mandiant (a Google Cloud company) and SlowMist confirmed the attack path, and no further unauthorized transfers were detected after containment was completed.
Fund Security Protection
Vulnerability Identified and Fixed
The exploited third-party vulnerability has been fixed, all internal credentials have been reset and reissued, and withdrawal verification mechanisms for critical operations have been strengthened with multi-level approval requirements.
Fund Security Protection
Proactive Anti-Scam Notice: We Never Ask for Private Keys
Bitget will never ask users to transfer funds or disclose passwords, private keys, seed phrases, or verification codes under the pretext of "helping recover assets." Official updates are released only through verified channels.
Fund Security Protection
What Happened in the September Security Incident: A Brief Review
What Happened in the September Security Incident: A Brief Review
Confirmed Amount Transferred Out
$388M
Cold Wallet
Unaffected
User Account Balances
Unaffected
Withdrawal Services
Fully Restored
At 18:31 UTC on September 24, 2026, the attacker initiated the first unauthorized transfer from certain hot wallets and warm wallets. At 19:05 UTC, Bitget's reconciliation system identified a discrepancy in fund reconciliation (rather than the security system proactively detecting it). Approximately 34 minutes later, the risk control system automatically blocked withdrawal requests platform-wide. The attacker exploited a zero-day vulnerability in a third-party security product to steal internal network access credentials and forge withdrawal instructions, bypassing risk controls to complete the transfers. Private keys were not compromised, and the relevant vulnerability has been fixed. Read the full technical report →
Industry Comparison
Industry Comparison
Bitget's Response Mechanism vs. Common Industry Benchmarks
What has changed since the incident?
What has changed since the incident?
“
Latest update: Withdrawals for all cryptocurrencies, fiat currencies, and P2P services were fully restored on October 2, 2026; the exploited vulnerability has been fixed; internal permission controls have been comprehensively reviewed; and the Bitget Protection Fund has been replenished to a level above that before the incident.
Whether to continue holding funds on any exchange is a personal risk decision. This page and the related Bitget security incident page provide verified facts—the purpose is to help you make an informed decision based on the latest information, rather than on information that became outdated during the incident.
Whether to continue holding funds on any exchange is a personal risk decision. This page and the related Bitget security incident page provide verified facts—the purpose is to help you make an informed decision based on the latest information, rather than on information that became outdated during the incident.
Frequently Asked Questions
Is Bitget still safe now?
Yes, based on the facts verified to date. The September 24, 2026 incident affected only certain hot wallets and warm wallets; cold wallets and user account balances were not affected. The exploited vulnerability has been fixed and independently verified by Mandiant and SlowMist. No new unauthorized activity has been detected since containment. This incident exposed a specific third-party component risk, not a flaw in Bitget's asset custody architecture—and that core architecture withstood the test during the incident. Withdrawals have been fully restored, and the financial impact of this incident is covered by the Bitget Protection Fund. For complete evidence, see the six key protection mechanisms above.
Can Bitget still be trusted after the hack?
Yes. This incident exposed a vulnerability in a third-party security product, not a failure in Bitget’s own asset custody design: the cold wallets holding most of the platform’s assets were never affected, no user funds were lost, and the exploited vulnerability has been fixed. Two independent cybersecurity firms, Mandiant and SlowMist, reviewed the response and confirmed that no new unauthorized activity was detected after containment. The way Bitget handled this incident—rapid containment, full transparency throughout, and replenishing the Bitget Protection Fund to above its pre-incident level—is the clearest proof of how the platform protects users when issues arise.
Will Bitget go bankrupt or run off with users' funds?
Based on currently disclosed financial information, there are no indications of this. The Bitget Protection Fund alone holds more than the confirmed amount affected by this incident. As of the latest financial report, Bitget’s own funds, including the Bitget Protection Fund, exceed $1.4B. Trading and deposit services remained operational throughout the incident.
Is Bitget a scam?
No. This was a security incident—attackers exploited a third-party vulnerability to steal credentials and forge withdrawal instructions. It was not a case of platform insolvency, an exit scam, or misappropriation of user funds. User account balances were unaffected throughout, and the incident has been independently investigated by Mandiant and SlowMist.
Are my funds/account balance on Bitget safe?
Yes. Account balances remained accurate and unaffected throughout the incident. Approximately $388M in affected funds came from hot wallet and warm wallet infrastructure, not user balances. The resulting financial impact is covered by the Protection Fund and will not be passed on to users.
Is now a good time to return to Bitget?
Yes. The phased withdrawal restoration plan was fully completed on October 2, 2026, withdrawals for all supported assets have returned to normal, and the exploited vulnerability has been fully fixed. The standards demonstrated by the platform's response—rapid containment, independent verification, and replenishing the Protection Fund to above its pre-incident level—are the same security standards that were maintained throughout the incident. There are no outstanding issues that require you to continue waiting.
After this incident, is Bitget safer or less safe than its peers?
We will not name or rank specific peer platforms, but across every key dimension, Bitget's response in this incident exceeded common industry practices: detection and containment within one hour, zero loss to user account balances, full public release of two independent forensic reports, and uninterrupted monthly Proof of Reserves publications throughout the incident. See the item-by-item comparison in the "Industry Comparison" section above.
Which exchange is the safest in 2026?
This page does not rank exchanges by name, but it fully documents Bitget’s specific response to the September 2026 incident across six protection dimensions (wallet architecture, fund coverage, reserve transparency, incident response, vulnerability remediation, and user protection), each supported by verifiable sources. It met high standards simultaneously in response speed, transparency, and independent verification.
Should I move my funds from Bitget to another exchange?
There is no factual basis for doing so. The cold wallets holding the majority of the platform's assets were never accessed, private keys were not compromised, user account balances were unaffected, withdrawals have been fully restored, and the vulnerability that caused this incident has been fixed. Moving funds elsewhere does not eliminate the same type of risk—every exchange operates hot wallet infrastructure—and Bitget has proven in a real-world scenario that it can contain and resolve such risks.
Is Bitget regulated? Does it hold licenses?
Yes. Bitget holds regulatory licenses and registrations issued in multiple jurisdictions and operates in accordance with applicable regulatory requirements. This security incident is unrelated to the platform’s regulatory compliance status—the incident resulted from the exploitation of a vulnerability in a third-party security product, not from any issue with the platform’s qualifications or licenses.
View the complete incident record
This page summarizes security evidence only. For the complete timeline, technical details, and fund tracing, please refer to the authoritative sources below.