Bitget raises breach estimate to $387.5M and launches recovery bounty
Bitget revised its estimate of the security incident to $387.5 million and said the vulnerability had been identified and fixed. A separate analysis put the affected assets at about $388 million after adding Zcash and TRON holdings that were not counted before, while GoPlus said the event involved compromised wallet back-end systems and falsified transaction data rather than a private-key leak.
What this rests on
What it means
Each sentence links inside to the piece that supports it.
Bitget users and wallet customers are the main people who would notice this next, because the incident now sits alongside a stated recovery bounty and a fixed vulnerability. The practical effect is that the event is being framed around a repaired weakness and asset recovery work rather than an open technical gap.
What changes in practice is the scope of what is being counted: Zcash and TRON assets were added to the estimate, and the revised total did not reflect a new theft. That still leaves the basic incident in place, but the tally attached to it is different from the earlier figure.
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 Briefing
scoop
Cointelegraph
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 3.9 years ago | FTX · Phishing incident | $450M |
| 5.8 years ago | OneCoin · Scam incident | $440M |
| 23 days ago | Bitget incident | $351.6M |
| 4.7 years ago | Portal · Signature Verification Flaw incident | $326M |
| 41 days ago | Liquid Network incident | $320M |
4197 incidents stored · 20 were as large as this one or larger ($388M)