Daily Crypto Briefs 
VICTORIA, Seychelles, September 25, 2026
Bitget raised its confirmed estimate of crypto sent to attacker-controlled addresses in a September 24 wallet breach to about $387.5 million on Friday, while withdrawals remained paused and its BGB token traded below its price before the attack.
As of 16:00 UTC September 25, the exchange’s latest update increased the figure by $35.9 million from its initial $351.6 million estimate. Bitget said the revision captured Zcash and TRON assets missed in the first accounting, not another wave of unauthorized transfers. It said it would announce the status and timing of withdrawals by 4:00 a.m. UTC on September 26, without promising that withdrawals would resume then.
Bitget’s BGB price history shows the exchange token closed September 24 at $1.96, down from $2.04 the previous day, a decline of about 3.9%. It touched $1.89 during the day, while reported trading volume rose to $43.83 million from $14.87 million on September 23. Those market moves coincided with the breach; the data alone cannot establish how much of the change the incident caused.
Bitget said its latest onchain tracing and transaction classification confirmed assets equivalent to about $387.5 million were transferred to addresses controlled by the attacker. The exchange published receiving addresses on EVM networks, XRP Ledger, Zcash and TRON, giving investigators and other platforms specific destinations to monitor. Its figure is an estimate of affected assets, not a final statement of unrecovered loss.
The breach was first detected at 18:31 UTC on September 24, according to Bitget’s original security notice. The exchange said a portion of its hot and warm wallet systems was affected, while cold wallets remained secure. The jump to $387.5 million is a material change in the accounting of that event, rather than a second reported attack.
Bitget Token
BGBBitget’s Revised Hack Loss Includes Zcash and TRON
Bitget named XRP, ether, USDT, ZEC, USDC, USDT0, tokenized gold XAUt, BNB, AVAX and TRX among the affected assets. It did not publish an asset-by-asset dollar breakdown, an affected-customer count or a figure for the funds still under the attacker’s control after freezing efforts. That limits any independent calculation of the final net loss.
The company said its team had identified and fixed the underlying vulnerability and that further unauthorized transfers were no longer possible. It named Mandiant and SlowMist as independent experts working on the investigation. Bitget has not yet published a full technical account showing how the attacker first gained access or bypassed its controls, so the precise entry route remains unverified publicly.
The published receiving addresses strengthen the loss-impact picture beyond a description of a software flaw: Bitget says assets actually moved to attacker-controlled destinations across multiple networks. The situation differs from incidents where a vulnerability is found before any theft. Its scale also follows a year in which crypto hacks had already set a first-half record, although the causes of those attacks vary.
Withdrawals Stay Paused as Bitget Starts Recovery Bounties
Bitget says customer balances remain accurate and that its User Protection Fund, valued at more than $464 million in its initial notice, covers the loss. That claim puts the fund roughly $76.5 million above the revised gross transfer estimate, based on the company’s own numbers. Bitget has not published an independent final audit showing how much it has recovered, how liquid the fund is or whether any customers will need reimbursement.
Deposits and trading remained operational, the exchange said, even as withdrawals stayed suspended for security checks. A frozen withdrawal channel has a direct customer impact regardless of whether balances remain visible. Previous exchange withdrawal and outflow episodes show why users should distinguish reported reserve balances from their ability to move assets; the causes and scale of those episodes were different.
Bitget said some affected assets have been frozen with industry partners but did not give a dollar value. Its new recovery program offers a potential 5% bounty on eligible funds frozen and another 5% on funds recovered, with eligibility decided by Bitget. The company said court-ordered or law-enforcement-directed actions are excluded. The bounty is a recovery incentive, not evidence that a stated amount has already been returned.
Bitget Wallet Users Face a Separate Risk Picture
Bitget Wallet said its separate self-custody systems and users’ onchain assets were unaffected by the exchange breach. That statement concerns the wallet product, where users control their own keys; it does not reopen withdrawals for assets held in exchange accounts. The wallet team warned users against fake “security verification” and “asset migration” messages, a concern that has also followed other crypto platform breaches.
The broader market’s Crypto Fear and Greed Index stood at 71, or “Greed,” on September 25. That market-wide reading is not a measure of confidence in Bitget or a forecast for BGB.
Fear & Greed Index
Sep. 25, 2026The next concrete test is Bitget’s promised withdrawal-status announcement by 4:00 a.m. UTC September 26. Investigators also have yet to disclose a verified final recovery total, customer impact count or complete root-cause report. Those disclosures will show how much of the $387.5 million in traced transfers remains an economic loss and when users regain access to withdrawals.
Stay up to date
Get the latest crypto insights delivered to your inbox
Primary sources and further reading
| Source | Title |
|---|---|
| | Bitget: fund tracing and recovery bounty update |
| | Bitget: initial exchange wallet incident notice |
| | Bitget Wallet: self-custody security statement |
| | Bitget: BGB historical price data |
| | Alternative.me: Crypto Fear and Greed Index |
Fact-checked by: Daily Crypto Briefs Fact-Check Desk
Related Articles
Frequently Asked Questions
How much was stolen in the Bitget hack?
As of Bitget's September 25, 14:05 UTC update, it had confirmed assets worth about $387.5 million transferred to attacker-controlled addresses. Its earlier estimate was $351.6 million. The new tally adds Zcash and TRON assets from the same incident.
Are Bitget withdrawals available?
Bitget said withdrawals were still paused during security checks. It promised to announce their status and timing by 4:00 a.m. UTC on September 26, 2026; that is an update deadline, not a guaranteed reopening time.
Did the Bitget breach affect customer balances?
Bitget says customer account balances remain accurate and the loss is covered by its User Protection Fund, which it values above $464 million. The exchange has not published an independent final loss audit or a count of affected customer accounts.
Was Bitget Wallet hacked too?
Bitget Wallet says its separate self-custody infrastructure and users' self-custodied assets were not affected by the Bitget Exchange incident.
Did a second attack raise the loss to $387.5 million?
Bitget says no. It attributed the $35.9 million increase to fuller classification of transfers during the original breach and says the incident has been contained.