Bitget has confirmed a roughly $351.6M security breach involving parts of its hot and warm wallet infrastructure.
Withdrawals were suspended after unauthorized transfers were detected, while deposits and trading remained operational.
Bitget says its cold wallets were not affected and its User Protection Fund currently holds more than $464M, which it says is enough to cover the estimated loss. The exchange is still investigating exactly how the attack happened.
Personally, the biggest issue here isn't just the $351M headline.
It's operational security.
An exchange can have billions in assets and still have a vulnerable layer sitting between its wallet infrastructure and signing system. Early reports point toward a compromised third party tool generating fraudulent transfer information, rather than a straightforward private key leak.
That's an important distinction, but it doesn't make the incident less serious.
And this is where proof of reserves alone doesn't answer everything.
Users also need to understand how exchanges secure hot wallets, control signing permissions and respond when abnormal transactions start moving funds.
The protection fund may cover the loss.
But trust is harder to replenish.
For now, I'm watching two things: how quickly withdrawals return and whether Bitget's final post mortem explains exactly where the security failure happened.
Because in crypto, “funds are protected” is a statement.
The investigation is what has to prove it.
$BTC #BTC Price Analysis# $BGB #Macro Insights#
Withdrawals were suspended after unauthorized transfers were detected, while deposits and trading remained operational.
Bitget says its cold wallets were not affected and its User Protection Fund currently holds more than $464M, which it says is enough to cover the estimated loss. The exchange is still investigating exactly how the attack happened.
Personally, the biggest issue here isn't just the $351M headline.
It's operational security.
An exchange can have billions in assets and still have a vulnerable layer sitting between its wallet infrastructure and signing system. Early reports point toward a compromised third party tool generating fraudulent transfer information, rather than a straightforward private key leak.
That's an important distinction, but it doesn't make the incident less serious.
And this is where proof of reserves alone doesn't answer everything.
Users also need to understand how exchanges secure hot wallets, control signing permissions and respond when abnormal transactions start moving funds.
The protection fund may cover the loss.
But trust is harder to replenish.
For now, I'm watching two things: how quickly withdrawals return and whether Bitget's final post mortem explains exactly where the security failure happened.
Because in crypto, “funds are protected” is a statement.
The investigation is what has to prove it.
$BTC #BTC Price Analysis# $BGB #Macro Insights#
