Binance Sets Aside $6.34 Billion After Hack Tied to DevOps Laptop

Binance has reserved more than $6.34 billion of its own funds to cover losses from a major hack. The money comes from company resources, not from a pass-through to users, and it shows how large the incident is.

Investigators are now focusing on a compromised laptop used for DevOps work. How a single endpoint could open a path toward systems linked to such a vast sum is the central question in the case.

Parallels with the Bybit attack

Similarities with the Bybit attack are raising questions about custody controls. The comparison points to a possible weak spot that lies less in the blockchain itself and more in the devices, people and internal tooling around signing and approval processes. The exact technical route has not been made public, and the investigation has not yet delivered final findings.

Why it matters

For customers, the size of the reserve is the key signal: Binance is absorbing the losses on its own balance sheet. For the wider industry, the case reopens the debate over how exchanges separate developer machines from systems that can move funds, and how many independent approvals a transaction should require.

The incident also feeds a forward-looking concern: authorization for AI agents. As companies consider letting automated agents act on infrastructure or payments, the question of what those agents may approve, and how their permissions are verified, becomes more pressing if one compromised device can already cause damage on this scale.

What comes next depends on what the investigation finds about the laptop and any link to the Bybit case. Those findings are likely to influence custody practices well beyond Binance.