# Binance Says a $6.3 Billion Attack May Have Started on One Engineer's Laptop

_On October 30, 2026, Binance said a compromised DevOps engineer's laptop may have let an attacker gain access to a service container and submit unauthorized withdrawals. It puts the impact at about $6.3 billion. Its co-CEO later said the attacker did not simply use that engineer's permissions._

By Johannes Keienburg, CEO & Founder  
Published: 2026-11-05  
Source: https://www.cakewalk.security/blog/binance-devops-laptop-6-3-billion-withdrawals

---

## A Compromised Laptop May Have Opened the Way to Binance's Withdrawals

On October 30, 2026, the cryptocurrency exchange Binance said an attack with an estimated impact of about $6.3 billion may have started on one employee's laptop. The laptop belonged to a DevOps engineer, one of the staff who build and operate the systems a company's software runs on. According to Binance's initial investigation, the compromised laptop let an attacker gain access to a service container, a packaged environment that runs a single piece of software. From that container the attacker submitted unauthorized withdrawal transactions. Binance's first account puts [one person's work machine](/blog/cert-fr-app-data-breaches-valid-accounts) at the start of the attack.

> We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.

_Binance, Security Incident Update (2026-10-30), October 30, 2026_

Binance says it has frozen about $3 billion of the affected assets on-chain, working with blockchain partners. As immediate precautions in its [incident response](/glossary/incident-response), it suspended withdrawals while security checks ran and brought in law enforcement and blockchain intelligence partners to trace the funds. Binance says user funds are safe and that it will cover all losses from the SAFU fund and the company's funds. It says deposits remain unaffected.

## Binance's Co-CEO Says the Attack Went Beyond One Engineer's Permissions

Hours after the announcement, Richard Teng, Binance's co-CEO, [repeated the laptop account on X](https://x.com/_RichardTeng/status/2116072080525656150) and added that the attack went beyond the engineer's own access.

> To be clear: the attacker did not simply use one engineer's permissions, and this was not a single 'one-click' action. It involved a more complex attack process. Our investigation has not attributed responsibility to any individual.

_Richard Teng, co-CEO of Binance, on X, October 30, 2026_

About an hour after Teng's post, Binance [wrote on X](https://x.com/binance/status/2116089661408108712) that its subsequent investigation had uncovered additional points of breach beyond the laptop. Binance described the incident as a complex attack and said the outflows stopped once it paused the withdrawal service. What those additional points of breach were, and how the attack moved from the laptop to the withdrawals, wait for the post-mortem Binance has promised.

> Binance says the attacker went beyond the engineer's own permissions. A takeover on a laptop also files no access request that anyone could deny. What a company can settle in advance is what each account in its connected apps holds on the day a laptop is taken over. In Cakewalk's Human Access product, access to a connected app can carry an end date that an approver can only shorten. Once that date passes, the product raises a removal nobody can decline, which Cakewalk's automation carries out where it is set up for that app and a person handles elsewhere. The requester and the approver both stay named on the request.

_Comment from Gil Röder, CPO & Co-Founder_

Source: Binance, [Security Incident Update (2026-10-30)](https://www.binance.com/en/support/announcement/detail/c5a8729a97ac486d963784d96c5642d7), October 30, 2026.
