According to Binance’s initial investigation, the security incident may involve a compromised DevOps engineer’s laptop. Through it, an attacker gained access to a service container and submitted unauthorized withdrawal transactions. Binance says it found no evidence of a wallet private key leak.
Binance estimates the total impact at around $6.3B, with about $3 billion frozen on-chain so far together with blockchain partners. It says it will cover all losses from the SAFU fund and company funds, and that user funds are safe.
Binance temporarily suspended deposits and withdrawals, revoked the affected address authorisation and engaged law enforcement and blockchain intelligence partners to trace funds. It plans to publish an updated Proof of Reserves after remediation and a technical post-mortem once the facts are verified.
For your organisation, the lesson is that one endpoint can open the way to production systems. Review which access engineers’ devices have to containers and transaction flows, and apply strong authentication and least privilege. Make sure your incident response plan covers fast containment and clear communication. Also remind customers to rely only on official channels, as Binance advises.
Read x.com article for more information.
