PiCK
Bitget CEO Gracy Chen Says No Private-Key Leak as Exchange Identifies Part of Attack Route
Summary
- Bitget said it has identified part of the attack route tied to a recent large-scale fund outflow incident and ruled out the possibility of a private-key leak.
- Chief Executive Officer Gracy Chen said a hacker breached a core backend system of the wallet service, generated fake transfer data, and invoked the approval-signature process to move funds off the platform.
- Bitget said it has completed measures to prevent further losses, leaving no risk of additional fund outflows, while work on resuming withdrawal services and strengthening security continues.
Forecast Trend Report by Period



Bitget said it has identified part of the attack route behind a recent large-scale fund outflow incident. The company said it has ruled out the possibility of a private-key leak and blocked the risk of any additional asset losses.
Bitget Chief Executive Officer Gracy Chen wrote on X on Sept. 25 that the security team identified the source of the attack at an early stage. A hacker breached one of the wallet service's core backend systems, then used that system to generate fake transfer data and invoke the approval-signature process to move funds off the platform.
Chen said the possibility of a private-key leak can be ruled out. She emphasized that this means a more serious risk scenario did not occur.
Measures to prevent further losses have been completed, and there is no risk of additional fund outflows from the platform, she said. The exact method the hacker used to breach the system is still undergoing technical verification, and the full findings will be disclosed later in an incident report.
Work to resume withdrawals is also under way. Multiple technical teams are simultaneously working on system recovery, security upgrades and preparations to restart withdrawal services, Chen said.
She did not provide a specific timeline. Chen added that the company will announce one as soon as a clear schedule is set and will not promise a timeframe it cannot meet.
YM Lee
20min@bloomingbit.ioCrypto Chatterbox_ tlg@Bloomingbit_YMLEE