Binance says it has recovered roughly $2.85 billion of the $6.34 billion it lost in a multi‑stage supply‑chain attack, yet the exchange’s public assurances stop short of guaranteeing that ordinary traders will see their money back. The gap between the recovered amount and the total loss is not a bookkeeping curiosity; it is a bill that will be paid by the very users who trusted the platform with modest savings.
The timeline Binance now admits
According to the post‑mortem that Binance posted on X (formerly Twitter) – the thread authored by @cyber_razz – the intrusion began in June 2024 when an engineer, hunting for an AI‑coding helper, downloaded a tampered Homebrew installer. The malicious package slipped past Binance’s endpoint defenses, giving the attackers a foothold inside the wallet team’s development environment.

In September, a second engineer was lured via a legitimate‑looking job platform. The recruiter posed as a project director, conducted a live video interview, and then sent a take‑home assignment. The assignment replaced the legitimate pyenv tool with a malicious copy, and Binance’s security scanners failed to flag it.
By 20 October, the attackers used the compromised laptop and Binance’s own internal AI tool to reach two more wallet engineers. One of those engineers had a container‑deployment token stored locally, which the intruders harvested. On 29 October at 20:05 UTC, a container was deployed, the signing service was accessed, and funds began streaming out of the hot wallet.
Binance halted withdrawals shortly thereafter, but the on‑chain contract the attackers had already authorized continued to move assets. Because the wallet relies on Multi‑Party Computation (MPC), no single private key exists to instantly revoke the contract, forcing Binance to design a bespoke revocation procedure while the money was still flowing. The last stolen ETH left the system almost four hours after the first transfer.









































