# "private key" (compromised OR stolen OR leaked) — X 热门讨论 (2026-09-29 08:12 UTC)
## @Promirexy (Crypto_Rexy🧘♂️) · 09-29 04:55 · ♥175 ↻4 💬216 Bitget now says how the 387.5 million dollars actually left
Not a copied private key
A third party security product, stolen internal credentials, fake withdrawal commands their own system ran
Onchain shows how fast it moved
🧵🧵🧵 https://t.co/IwrZpg9rhE > 引用 @Promirexy: Gm legends 🧘♂️
Here’s what Bitget has scheduled for today
07:30 UTC: livestream with @GracyBitget Incident report and withdrawals
08:00 UTC: BTC withdrawals due to reopen Bitcoin network only
ETH is 29 Sept USDT is 30 Sept The rest is 2 Oct
Scheduled is not the same as live
Check the app after 08:00
Still ignore recovery DMs Only @bitget and @GracyBitget https://x.com/Promirexy/status/2104797130154258491
## @BullbitDEXHQ (Bullbit PERP DEX) · 09-28 03:34 · ♥20 ↻4 💬3 What if the weakest point in custody isn’t the private key?
CEX custody has come a long way in protecting keys, but custody security involves more than where the key is stored. There’s also the layer that determines which transactions reach the signer in the first place: a part of the system users rarely get to see.
So what happens when the key stays secure, but the instruction itself is compromised?
The piece explores transaction authorization, where this risk sits in CEX infrastructure, and how the trust model changes when signing authority stays with the user.
See the full breakdown ↓ > 引用 @BullbitDEXHQ: Beyond Key Custody: How Transaction Authorization Becomes the Weak Point https://x.com/BullbitDEXHQ/status/2104414504385946021