Developing story. Binance has not yet published its full technical post-mortem. We update this article as facts are confirmed.
The Binance hack on October 29, 2026 moved roughly $6.3 billion out of Binance-controlled wallets across ten blockchains in about 20 minutes. Binance puts the damage at about $6.3 billion. TRM Labs counts $6.36 billion and Elliptic counts $6.43 billion, which is more than four times what was taken from Bybit in 2025. Nothing bigger has ever been reported in crypto.
The number grabs the headlines, but the method is what matters to anyone in security. Nobody cracked a customer’s password. The attackers got Binance’s own systems to approve transactions they should never have approved.
This post covers what’s known, what isn’t, and what any team running sensitive infrastructure can take from it.
The short version
Roughly $6.3 billion left Binance hot wallets in about 20 minutes. Binance says the breach may have started with a compromised DevOps engineer’s laptop, but it has since admitted investigators found more breach points than that. On Ethereum, a feature called EIP-7702 let the attacker hijack one hot wallet. TRM Labs and Chainalysis blame North Korea’s TraderTraitor group, though Binance hasn’t confirmed it. About $3 billion has been frozen, and Binance says it will cover user losses from its SAFU fund and company money. That’s the whole Binance hack in a paragraph. The details are below.
What happened in the Binance hack?
Funds started moving out of Binance hot wallets around 20:05 UTC on October 29. Within about 20 minutes, assets had left Ethereum, Bitcoin, Tron, the XRP Ledger, Solana, Arbitrum, Optimism, Base, Avalanche and Polygon.
A hot wallet is a wallet that stays connected to the internet so an exchange can process withdrawals quickly. Most of an exchange’s funds sit offline in cold storage, but hot wallets still hold a huge amount, and because they have to stay online they’re the obvious target.
Binance confirmed the incident on October 30, paused withdrawals as a precaution, and said it found no evidence that wallet private keys had leaked.
Binance hack timeline (UTC)
| When | What happened |
|---|---|
| Oct 28–29 | Attacker wallet funded through Tornado Cash. TRM says preparation began at least 36 hours before the theft |
| Oct 29, ~15:59 | Sweeper contract deployed. Elliptic says it was rehearsed on another wallet about four hours earlier |
| ~20:05 | Transfers begin on the XRP Ledger and other chains |
| ~20:20 | One transaction carrying 50 EIP-7702 authorizations lands on Ethereum |
| ~20:24 | The “Binance 14” hot wallet is emptied: 167,464 ETH and 63 tokens, including about $1.6B in USDT |
| 20:41–23:56 | More sweeps of fresh deposits. The delegation stays live for nearly four hours before Binance revokes it |
| Oct 30 | Binance confirms the incident, freezes funds with partners and says it found additional breach points |
Times come from TRM Labs and Elliptic. The sources differ slightly on how many follow-up sweeps there were.
How did the hackers get in?
Binance’s first explanation was a compromised laptop belonging to a DevOps engineer. The idea is that the attacker used it to reach an internal service container and, from there, submitted withdrawals nobody had approved.
DevOps people sit where code, cloud and production meet, so one infected workstation can open doors it was never supposed to. That’s why this lead is being taken seriously.
Two things to keep in mind. First, Binance hasn’t said how the laptop was compromised. It could have been phishing, malware, a stolen session or something else, and anyone claiming to know is guessing. Second, the laptop is the door, not the whole building. Co-CEO Richard Teng has said it was a more complex attack than one engineer’s permissions or a single click, and that investigators found additional points of breach.
A valid signature isn’t the same as a legitimate transaction
Every crypto transaction needs a valid signature, and the blockchain checks it. What the blockchain can’t check is whether the company really meant to send the money.
So if an attacker gets a company’s own signing system to sign the wrong thing, the network accepts it and everything looks perfect on-chain.
This is where the story gets odd. Elliptic says the 50 authorizations in the Ethereum attack were validly signed with the key of the Binance 14 hot wallet, yet Binance says it has no evidence that keys leaked. Our reading, and it is only a reading, is that the attacker didn’t steal the key. They got hold of the system that uses it. That would explain why the investigation is focused on signing infrastructure and not just key storage.
What is EIP-7702 and how was it used in the Binance hack?
EIP-7702 is an Ethereum upgrade that went live in May 2025 with Pectra. It lets an ordinary wallet borrow the behavior of a smart contract for a while, which is handy for batching transactions and building smarter wallets. The catch is that whoever holds a valid authorization to point a wallet at their own code controls what that wallet does.
Here’s what the attacker reportedly did on Ethereum:
- Prepared a sweeper contract, which is code built to push a wallet’s assets to an address the attacker controls.
- Pre-signed 50 authorizations covering consecutive nonce values. A nonce is just a transaction counter, so only one had to match the wallet’s current value. Sending 50 made sure one would land.
- Sent them all in one transaction. Ethereum accepted the matching one, and the Binance 14 wallet started running the attacker’s code.
- Emptied the wallet about three and a half minutes later: 167,464 ETH and 63 tokens, including roughly $1.6 billion in USDT, in a single transaction.
- Left the delegation in place. Because it stayed active, new deposits kept getting swept without any new signatures, and Elliptic says the attacker also used Binance 14’s owner rights to pull hundreds of millions in USDC out of another Binance wallet.
One thing people keep getting wrong online: EIP-7702 didn’t cause the whole Binance hack. It’s a known Ethereum feature, not a flaw in Ethereum, and TRM says the other chains saw ordinary signed transfers. The real problem was the attacker’s ability to get valid authorizations out of Binance’s systems. EIP-7702 just made one big wallet very easy to empty.
Who is behind the Binance hack?
TRM Labs attributes the operation with high confidence to TraderTraitor, a North Korea-linked group that investigators tied to the roughly $1.5 billion Bybit theft in February 2025. Chainalysis and Elliptic also point toward North Korea-linked actors. TRM bases its call on on-chain and off-chain intelligence, plus habits shared with earlier cases: long preparation, signatures collected in advance and wallets funded through a mixer.
Treat that as an intelligence assessment, not a verdict. Binance hasn’t officially confirmed it, and no individual has been named.
Where did the stolen crypto go?
Taking the money was the first step. Keeping it was the hard part. According to TRM, the attackers split Bitcoin through peel chains, where funds move through long strings of smaller transactions to make tracing harder. They also tried swapping USDT into other assets before issuers could freeze it, and they used DeFi services including UniswapX, Aave and JustLend to shuffle value around.
It was basically a race against investigators, exchanges and token issuers. Binance says about $3 billion has been frozen, and TRM counted $2.7 billion at an earlier cutoff. A lot of the haul was in stablecoins, which issuers can freeze, and that helped. TRM lists Tether, Circle, Ripple, World Liberty Financial and Arbitrum’s Security Council among the partners that froze assets.
Frozen doesn’t mean recovered, though. A freeze stops the money from moving. Who gets it back, and when, is a separate legal fight that can take a long time.
Is your money safe on Binance?
Binance says customer funds are safe and that it will cover the losses from its SAFU emergency fund and company funds. It also says it’s working with law enforcement and plans an updated Proof of Reserves and a technical post-mortem. That’s the company’s position, not independent confirmation, and none of this is financial advice.
What we can say from a security angle is that big breaches bring out the scammers. Expect fake messages about compensation, restored withdrawals or “verify your account”. Binance users were already getting phishing texts and fake domains before this. Stick to the official app, type the URL yourself, turn on a passkey or hardware security key plus Binance’s anti-phishing code, and never hand a 2FA code to someone claiming to be support.
Security lessons from the Binance hack
These come from the reported attack. We’re not claiming to know every control Binance did or didn’t have.
- Treat engineer laptops as production-adjacent. EDR, device posture checks and fast isolation of suspicious machines all matter here.
- Use least privilege and just-in-time access. A laptop with standing access to production containers is a liability waiting to happen.
- Keep signing separate from application infrastructure. The signing layer should enforce its own rules, like limits, allowlists and independent approvals, instead of trusting whatever internal service asks.
- Watch for unexpected EIP-7702 delegations. An unplanned one on a treasury wallet should page someone immediately, and so should a batch of authorizations covering consecutive nonces.
- Catch it before the withdrawal. TRM says preparation started at least 36 hours earlier, with wallets funded through Tornado Cash and the contract rehearsed beforehand. Funding patterns, contract deployments and test transactions are all early warnings.
- Practice the kill switch. Teams should know how to revoke delegations, isolate wallets and pause withdrawals in minutes. Here the malicious delegation stayed live for nearly four hours.
Binance’s earlier hacks
This isn’t the first time. In May 2019, attackers took 7,000 BTC, about $41 million, from a hot wallet, and Binance blamed phishing, viruses and other attacks. It said the hackers were patient and worked through many seemingly unrelated accounts. In October 2022, about $570 million in BNB was minted from the BNB Chain bridge by forging a proof, which was a smart-contract bug and not phishing. Now, in October 2026, roughly $6.3 billion went out through trusted internal infrastructure and signing access. Three incidents, three completely different failure modes.
What we still don’t know
Four things are still open. How the laptop was compromised hasn’t been disclosed. Binance says there are additional points of breach but hasn’t described them. How the attacker got every valid authorization is still under investigation. And attribution and recovery totals are still moving. Posting a guess as fact is how security misinformation spreads, so it’s better to wait for the post-mortem.
Binance hack FAQ
How much was stolen in the Binance hack?
Binance says about $6.3 billion. TRM Labs says $6.36 billion and Elliptic says $6.43 billion. The gaps come from asset prices at the time and how each firm counted.
How did hackers get into Binance?
Early findings point to a compromised DevOps engineer’s laptop, used to reach an internal service container and submit unauthorized withdrawals. Binance later said investigators found more breach points. How the laptop was first compromised hasn’t been disclosed.
What is EIP-7702?
It’s an Ethereum feature that lets a wallet hand its actions to smart-contract code. The attacker used 50 pre-signed authorizations to make a Binance hot wallet run a malicious sweeper contract.
Who was behind the Binance hack?
TRM Labs and Chainalysis attribute it to North Korea’s TraderTraitor group. Binance hasn’t officially confirmed that.
Were Binance’s private keys stolen?
Binance says it has no evidence that private keys leaked. The attacker apparently got valid signing authorizations through Binance’s own infrastructure.
Can the stolen funds be recovered after the Binance hack?
About $3 billion has been frozen, but freezing isn’t recovery. Getting funds back needs separate legal processes and could take a long time.
Is my crypto safe on Binance?
Binance says user funds are safe and that it will cover losses through SAFU and company funds. That’s the company’s statement, and it hasn’t been independently verified. Watch out for scams that use the news as bait.
Final thoughts
The cryptography did exactly what it was built to do. It checked signatures. The failure sat upstream, in the chain of trust between a laptop, a container, a signing system and a wallet. The biggest risk may not be someone breaking into your infrastructure. It may be someone quietly gaining access to the systems your infrastructure already trusts.
We break down incidents like the Binance hack in plain English at iShowCybersecurity and on Instagram at @ishowcybersecurity.
Sources
- Binance: Security Incident Update (Oct 30, 2026)
- TRM Labs: North Korea steals $6.36 billion from Binance
- Elliptic: The largest theft in history
- CoinDesk: How one Ethereum permission let an attacker drain $2.5B from Binance
- CoinDesk: Binance uncovers wider breach
- CNBC: Billions in crypto frozen in Binance hack
- The Hacker News: Binance suffers security breach
- Euronews: How the Binance hack happened and who was behind it



