Bitget Hackers Hit Roadblocks as Exit Routes Close
- Published
Bitget’s Sept. 24 incident has been linked to earlier malicious activity and to access through third-party security devices. After the breach, wallets tied to the attackers have faced rejection while trying to move assets across chains, and the exchange incident has also been framed as a marker for how cross-chain markets are being used.
Key claims & sources
What it means
Bitget users and the exchange’s security teams are the clearest people affected today because the incident is tied to exchange wallet access and later efforts to move stolen assets. The Sept. 24 breach reached hot and warm wallets, and wallets linked to the attackers later ran into a blocked transfer route, which is the concrete change now visible to the people watching the case most closely.
In practice, the incident leaves in place a setting where cross-chain movement is still being attempted, but at least one route through Chainflip was rejected and returned. That means the immediate picture is not a full stop on movement across chains, but a visible obstacle on one path that was being used after the Bitget theft.
Market reaction i
Bitget Token fell 1.0% in the 4 hours after the first headline, after a flat 2 hours before.
48 prices, one every 30 minutes
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.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 2 days ago | B18 TimeBank · Unknown incident | $404.5k |
| 3 days ago | MORE Markets · Unknown incident | $308k |
| 3 days ago | Lighter incident | $10.4M |
| 3 days ago | Optimizely (OPTIMJACK) · Supply Chain Attack incident | $2.3k |
| 4 days ago | Luxor Commander · Unknown incident | no figure in dollars |
4332 incidents stored