The Biggest Crypto Heist Ever Didn't Need a Single Stolen Key

Binance crypto heist https://pixabay.com/photos/blockchain-technology-smart-bitcoin-3446557/

On October 29th, 2026, an attacker stole around $6.36 billion from Binance wallets in the largest cryptocurrency theft on record. Most of the stolen assets were moved within the span of roughly 20 minutes beginning around 20:05 UTC, highlighting the speed that sets many modern attacks apart from what defenses are built to handle. In response to the attack, Binance suspended withdrawals and pledged to cover customer losses.

Initial Story Comes Apart

Binance’s first explanation, based on its initial investigation, pinned the incident on the compromise of a single DevOps engineer’s laptop. However, Binance has since confirmed additional points of breach. “It’s very common for large organizations to find one person they can blame, and anybody working in security should watch for that,” says John Strand, Owner, Black Hills Information Security. “If compromising one employee’s laptop can bring down your entire security structure, you have problems that go well beyond that employee.”

The reality is that most major attacks are the result of much more systemic issues and gaps in security that plague organizations across all sectors. Blaming one person early on in the investigation limits what can be learned from an attack to prevent similar incidents in the future. Those who could benefit from keeping an eye on the situation may tune out if they believe the cause is unrelated to them or out of their control.

Authorized Theft Without Stolen Keys

This attack was able to be carried out due to compromised transaction-signing infrastructure, leading to the takeover of a Binance hot wallet. The hot wallet enables a signed authorization to grant a smart contract control over a regular wallet. The operator in this attack sent one transaction with 50 different authorizations to maintain at least one as valid by the time the transaction was executed.

So far in the investigation of this attack, no evidence has turned up of any leaked wallet keys. Rather, the operator compromised the hot wallet in order to repeatedly send its entire balance to an account controlled by the attackers. The blockchain infrastructure in place to secure transactions can only verify signatures, not intent; attackers exploiting flaws in the signature system are carrying out authorized actions after compromising the signature infrastructure.

The Established TraderTraitor Pattern

Investigation of this incident by multiple sources points to North Korea-linked actors. Chainalysis ties the attack to the Bitget theft of September 2026 attributed to the cybercrime group TraderTraitor. TRM Labs names the same actor in this incident, citing features matching previous attacks linked to North Korean threat groups, including the February 2025 Bybit hack that resulted in nearly $1.5 billion lost.

Binance has not confirmed the attribution, and some experts urge caution in assuming attribution too soon. “I’d also be careful about getting too far ahead of the investigation on attribution,” says Robert Coles, Senior Manager of Threat Intelligence Security at Black Duck, a Burlington, Massachusetts-based provider of application security solutions. “There are certainly indicators pointing toward North Korea, particularly given the history of targeting cryptocurrency organizations, but I’d like to see more of the technical details around the intrusion before drawing any firm conclusions.”

Freezes and What's Left

Issuers of stablecoins responded rapidly to the incident: Tether froze about 1.77 billion USDT and Circle froze around 825 million USDC. The attack also affected around $2.4 billion in currencies that cannot be frozen by the issuers, like Bitcoin and Ethereum. Binance holds a secure asset fund of $1 billion to back the pledge to protect customers from losses like those seen in this attack.

The Developer Endpoint Question

The investigation and developing information surrounding this incident have raised some concerns regarding the types of weaknesses that contributed or could have contributed to the attack. If compromised developer laptops can lead to significant breaches like this, it may be necessary to reexamine what sensitive areas they are able to reach.

This breach occurred as the result of a failure of multiple approvals within a single incident. “Exchanges should test whether one breach can compromise both a withdrawal request and the checks meant to stop it,” according to Jason Soroko, Senior Fellow at Sectigo, a Scottsdale, Arizona-based provider of comprehensive certificate lifecycle management (CLM). “Requiring several approvals offers little protection if the attacker can control them all. Independent checks on recipients, withdrawal limits, and automatic pauses for unusual transfers can help contain losses.”

Post-Mortem in Progress

The investigation into this incident is still ongoing, with many questions still hanging in the air regarding how exactly the unauthorized withdrawals were approved by Binance’s controls and how similar attacks will be prevented in the future. The speed of the attack hints at potential automation or AI use, but nothing in that vein has been proven. Gaps in disclosure slow down the rate at which defenders can learn lessons from attacks like this.

Author
  • PJ Bradley
    Contributing Writer, Security Buzz
    PJ Bradley is a writer from southeast Michigan with a Bachelor's degree in history from Oakland University. She has a background in school-age care and experience tutoring college history students.