BingX reported a hot-wallet security incident on September 20, 2024. PeckShield’s approximately $43 million loss figure was an early estimate, not the exchange’s confirmed final loss.
BingX’s notice said it had detected suspicious activity at about 04:00 UTC+8, initiated an emergency response and suspended withdrawals for checks. Statements about the extent of damage and compensation were the exchange’s own assurances.
A hot-wallet incident affects the exchange’s transaction infrastructure. Moving other assets or promising compensation does not independently establish the amount ultimately recovered or repaid.
At first, BingX expected withdrawals to resume within 24 hours. A later FAQ said withdrawals for a specified list of assets had resumed before September 21 at 08:30 UTC+8, with deposits for a listed set resuming on September 22 at 08:30 UTC+8. These were asset-specific notices, not proof that every service was restored at once.
The initial restoration estimate and compensation statements should be read against the later service notices, rather than retained as an unresolved promise.
Security Issues Continue To Plague Crypto Exchanges
BingX isn’t alone in recent security troubles. Last week, hackers stole $22 million from Indonesia’s Indodax exchange, while India’s WazirX lost a staggering $234 million.
Self-custody removes dependence on an exchange’s permission to withdraw, while placing responsibility for recovery information and signatures on the user. A wallet still needs to be used securely.









