Bitget Reopens Bitcoin Withdrawals as Protection Fund BTC Moves
- Published
- Updated
- Since then
- 4 new reports
Bitget said its Sept. 24 security incident was tied to a third-party vulnerability, and later said attackers used stolen internal credentials to forge withdrawal requests while private keys and cold wallets were not affected. The exchange then isolated affected systems, repaired the vulnerability, and began restoring withdrawals in stages, starting with bitcoin on Sept. 28. Separate updates put the affected amount at about $387.5 million and described the withdrawal restart as the first step after the freeze.
Key claims & sources
What it means
Before these steps, the exchange said it isolated affected systems, reissued internal credentials, and added independent verification for later withdrawals. In practice, that means the withdrawal process now includes extra checks that were not there before, while the exchange also said the private keys and cold wallets were not affected. What remains in place is the staged restart itself, with different assets returning on different dates rather than all at once. (per tokenpost.com)
Market reaction i
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 4.0 years ago | FTX · Phishing incident | $450M |
| 5.9 years ago | OneCoin · Scam incident | $440M |
| 44 days ago | Bitget · Internal system compromise incident | $351.6M |
| 4.8 years ago | Portal · Signature Verification Flaw incident | $326M |
| 2 months ago | Liquid Network · Unbacked Cross-Chain Mint incident | $320M |
4282 incidents stored · 22 were as large as this one or larger ($388M)