Bitget Hackers Hit Roadblocks as Exit Routes Close
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.
What this rests on
What it means
Each sentence links inside to the piece that supports it.
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
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.
Crypto Economy
Crypto Briefing
context
Cointelegraph
context
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 2 days ago | KolanHook (1.279453 ETH) incident | no figure in dollars |
| 3 days ago | UNCX Network V2 · Incorrect Share Accounting incident | $86k |
| 3 days ago | Pirate Chain · Transaction validation vulnerability incident | $10.7M |
| 4 days ago | Gamdom · Hot wallet server compromise incident | $4.2M |
| 7 days ago | Papertrade · Price manipulation incident | $1.3M |
4197 incidents stored