Bitget Exchange Reportedly Hacked For Over $170 Million
Users reported withdrawal problems at Bitget while on-chain data showed about $176 million moving from wallets labeled as the exchange’s over a roughly 20-minute span. The receiving address later made several swaps, and the reason for the transfers was still unclear. The movements involved several Bitget-labeled hot wallets and at least one cold wallet.
What this rests on
What it means
Each sentence links inside to the piece that supports it.
Bitget users are the most immediate audience here, because withdrawal problems were reported while large transfers from wallets labeled as the exchange’s were being tracked. That means customers watching their accounts would see activity tied to the platform, even though the transfer reason was not established.
In practical terms, the wallet movements were visible on-chain and involved several hot wallets and at least one cold wallet, so the picture is not just a single wallet event. What remains the same is that the transfers themselves are described as moving funds between addresses, while the purpose behind them is still not stated.
Market reaction
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
How the story was built
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.5 years ago | Beanstalk · Flashloan Governance Attack incident | $181M |
| 4.5 years ago | BeanstalkFarms · DAO + flashloan incident | $181M |
| 6.2 years ago | YFValue · Staking pool vulnerability incident | $170M |
| 8.7 years ago | BitGrail · Improper Access Control incident | $170M |
| 4.1 years ago | Wintermute incident | $160M |
4197 incidents stored · 46 were as large as this one or larger ($170M)