Bitget has recorded $463 million in net outflows following a hack that stole up to $388 million from the exchange. The numbers, which landed this week, give the clearest picture yet of how quickly users pull money when a major platform gets breached. The theft itself is the headline. The withdrawal queue is the story.
The gap between what was stolen and what left
The $463 million figure is larger than the $388 million maximum attributed to the hack, which tells you something about how these events work. Some of the outflow is users moving assets off Bitget out of caution rather than direct loss. Some is likely traders repositioning after the incident hit the wire. Either way, the exchange is now down nearly half a billion dollars in net deposits on top of whatever the attackers took.
That spread matters. A hack is a one-time hit. A run is a slow bleed that can last days or weeks depending on how the exchange handles communications and whether it can credibly guarantee that remaining funds are safe. Bitget hasn't given a timeline for when outflows might stabilize.
What third-party security actually means here
This incident puts a hard spotlight on the security vendors exchanges rely on. Most major platforms don't build every layer of their defenses in-house — they lean on outside firms for custody tooling, key management, monitoring, and audit work. When an attacker gets through, the question becomes which layer failed and who was responsible for it.
The facts here don't name those vendors, and Bitget hasn't publicly assigned blame. But the broader point stands: an exchange can have a spotless internal security team and still get rolled if a third-party integration has a hole in it. That's the uncomfortable part of the disclosure for every exchange watching this.
Trust is the asset that's hardest to re-deposit
Outflows of this size do more than dent a balance sheet. They signal that a meaningful slice of Bitget's user base decided the risk of staying outweighed the cost of leaving. Once that decision is made, getting those users back is a much longer project than patching whatever was exploited.
The exchange could still recover. Crypto users have short memories when a platform pays people back quickly and communicates clearly. But the $463 million number is already out, and it's the kind of figure that gets cited every time Bitget's name comes up in a due-diligence conversation for months.
What's left to find out
Two things are still open. First, whether Bitget can stop the outflows before they compound into a genuine liquidity problem — no exchange wants to be in a position where it has to pause withdrawals, and the company hasn't said anything about that risk. Second, whether the stolen funds get traced. Blockchain forensics firms usually publish flow analyses within days of a major hack, and those reports tend to shape how exchanges, law enforcement, and the affected users respond.
For now, Bitget is sitting on a $463 million hole in net flows and a $388 million theft it hasn't fully explained. The next concrete data point will be whether outflows continue at this pace into next week.
