Bitget Resumes Withdrawals After $388M Hack
Bitget resumes withdrawals after 388 million hack through a phased rollout, according to The Block's reporting, with the exchange committing to cover user losses via its protection fund rather than leaving the shortfall unaddressed.
Bitget resumes withdrawals after 388 million hack through a phased rollout that began in late September 2026, according to reporting from The Block. The exchange has publicly committed to covering user losses tied to the breach through its user protection fund, rather than leaving affected accounts to absorb the shortfall themselves. For traders who hold balances on Bitget — or on any centralized exchange — this is the kind of event worth understanding in some detail, because how an exchange handles the aftermath of a hack tends to matter more than the hack itself.
This is a developing story, and the publicly available reporting we’re working from focuses on two confirmed points: the phased withdrawal resumption and the loss-coverage pledge. We’re not going to speculate beyond that. What follows is what it means for people who actually have money sitting on exchanges like this one.
What actually happened?
Per The Block’s September 28, 2026 report, Bitget began restoring withdrawal functionality in phases following a security incident involving losses reported at $388 million. The exchange stated it would make affected users whole through its user protection fund, the kind of insurance-style reserve that several large exchanges maintain specifically for scenarios like this.
Beyond those two facts, we’d caution against assuming more than what’s been reported. We don’t have a confirmed breakdown of which wallets or chains were affected, a precise timeline for when the phased rollout completes, or independently verified reserve figures. If you’re trying to decide what to do with funds on the platform, go to Bitget’s own official site and status channels for the most current operational detail rather than relying on secondhand summaries, including this one.
Why do exchanges suspend withdrawals after a hack in the first place?
A withdrawal freeze right after a breach is standard incident-response practice, not necessarily a sign that an exchange is in trouble. The logic is straightforward: if an attacker has compromised hot wallets or internal systems, keeping withdrawals open risks letting more funds flow out while the exchange is still investigating scope and patching the hole. Pausing withdrawals, auditing the breach, and then reopening in phases, often starting with lower-risk assets or smaller amounts, is a more controlled way to resume service without reopening the same vulnerability.
That’s a different situation from an exchange halting withdrawals because it’s actually insolvent or unable to cover client balances. The distinction matters, and it’s one we’ve written about before in the context of the biggest crypto exchange hacks, ranked, some incidents end in full reimbursement and a return to normal operations, others end in platforms disappearing entirely. A phased resumption paired with a public reimbursement commitment, which is what’s reported here, sits closer to the former pattern than the latter.
What should traders actually check before acting?
If you have an account on Bitget, or you’re evaluating whether to open one, a few practical steps matter more than headlines:
| Check | Why it matters |
|---|---|
| Current withdrawal status on Bitget’s own channels | Phased rollouts change day to day; third-party summaries lag |
| Any official statement on reimbursement timeline | Commitment to cover losses is not the same as funds already distributed |
| Your own transaction history on the platform | Confirms whether your specific balance was affected |
| Proof-of-reserves or audit updates, if published | Independent verification carries more weight than a press statement |
| Withdrawal limits or regional restrictions during rollout | Phased resumptions sometimes stagger by asset or geography |
Before depositing anywhere, not just Bitget, it’s worth running through a basic checklist. We cover this in more depth in how to check exchange security before depositing, which walks through what proof-of-reserves actually proves (and what it doesn’t), how to read an exchange’s incident history, and why insurance fund size alone isn’t a complete security signal.
How does this compare to how other exchanges have handled hacks?
Large exchanges including Binance and OKX maintain their own user protection or SAFU-style funds, designed for exactly this kind of scenario. When a breach happens, the two things that distinguish a well-handled incident from a badly-handled one are speed of transparent communication and whether the reimbursement commitment is actually followed through on, not just announced. Bitget’s public pledge to cover losses via its protection fund follows the same general playbook other major platforms have used in past incidents.
If you’re specifically weighing exchange security track records against each other, Bitget vs Bybit, or against OKX or Binance, our exchange rankings table and individual reviews for Bitget, Bybit, and OKX are a reasonable starting point, though we’d always recommend cross-checking against each exchange’s own current disclosures rather than relying solely on any third-party summary, including ours.
For traders who’d rather reduce exposure to any single platform’s incident risk altogether, spreading activity across more than one reputable exchange, or using a platform like BYDFi alongside a primary account, is a common risk-management approach, though it doesn’t eliminate counterparty risk entirely; it just avoids concentrating it in one place.
What’s next to watch
The two things worth tracking from here: whether the phased withdrawal rollout completes without further interruption, and whether Bitget publishes concrete follow-up, a completed reimbursement confirmation, an updated proof-of-reserves report, or a post-mortem on how the breach occurred. Those are the markers that separate a well-managed recovery from one that stalls. Until then, this reads as a serious but contained incident with a clear, publicly stated remediation path, not a platform in collapse. Traders with balances there should keep checking official channels directly rather than relying on any single report, including this one, as the final word.
If you’re newer to exchange security concepts generally, things like custody risk, hot vs cold wallets, or what an insurance fund actually covers, our beginner learning path and glossary are good places to build that baseline before the next incident, because there will be a next one somewhere in this industry.
Frequently asked questions
Is Bitget safe to use after the 2026 security incident?
Bitget has resumed withdrawals in phases following the hack and says it will cover affected user losses through its protection fund, per reporting from The Block. That said, any exchange that has suffered a breach deserves extra scrutiny for a while. Check current withdrawal status and any published audit updates before moving large balances.
How long did Bitget suspend withdrawals and are they fully resumed?
The Block reported that Bitget began a phased resumption of withdrawals following the breach, rather than switching withdrawals back on all at once. The exact duration of the initial freeze and the full completion date of the phased rollout were not detailed in available reporting, so traders should verify current status directly on Bitget before assuming full normal service.
Will Bitget reimburse users affected by the $388 million hack?
Yes. Bitget has publicly committed to covering losses tied to the incident through its user protection fund, according to The Block's coverage. The exchange has not, in the reporting available, broken down a per-user reimbursement timeline, so affected users should follow Bitget's official channels for specific claims guidance.
How does Bitget's security and SAFU fund compare to Binance and OKX in 2026?
Several large exchanges, including Binance and OKX, maintain user protection or insurance-style funds that are meant to backstop losses from hacks or exploits. Bitget's response after this incident — pledging full coverage via its own fund — follows that same general model. We don't have independently audited fund-size comparisons across exchanges, so treat fund size claims from any platform as advertised rather than verified.
Are Bitget withdrawals available in all countries following the 2026 incident?
Reporting on the phased resumption did not specify country-by-country availability. Exchanges sometimes stagger withdrawal access by asset, wallet type, or region during a recovery rollout, so users outside major markets should check Bitget's status page or support channel rather than assume uniform access.
What security audits or proof-of-reserves has Bitget published since the hack?
Available reporting on this incident, via The Block, focused on the withdrawal resumption and the loss-coverage commitment rather than a specific new proof-of-reserves report. Users who want current reserve data should check Bitget's own transparency or proof-of-reserves page directly rather than relying on secondhand summaries.
What should I do if I have funds on Bitget right now?
Check Bitget's official status page or app for current withdrawal availability before attempting a large transfer, and avoid depositing new funds until you're comfortable with the exchange's security posture. Spreading holdings across more than one reputable platform also reduces single-point-of-failure risk.
Does a hack like this mean an exchange is about to collapse?
Not necessarily. A hack followed by a transparent, funded reimbursement commitment is a materially different situation than an exchange going insolvent or halting withdrawals indefinitely. The key signals to watch are whether withdrawals actually resume as promised and whether the exchange follows through on its coverage pledge.