I want to talk about the Binance hack, because the market has already half moved on and the details deserve better. Six billion dollars left the exchange in 24 hours, according to DefiLlama, and that was before most people had worked out whether Binance was in trouble or just having a very bad day. It was a very bad day. By Thursday and into Friday, the company was putting the damage at roughly $6.3 billion, the largest exploit on record by its own description.
I've covered enough exchange breaches to know the first 48 hours say little about the cause and a lot about the balance sheet. So I'll start with the balance sheet.
The Market Flinched but Did Not Panic
The reaction was orderly, which is its own kind of tell. As Cointelegraph reported, BNB fell more than 8% over a day to about $693, Bitcoin slipped 4.8% to roughly $77,100, and Ether lost 5.7% to around $2,217. That is a nervous market, not a panicking one.
DeFi took the harder hit. Aave's AAVE token dropped 11.3% to $118.54, and Uniswap's UNI shed 10.4% to $6.48. The Bitcoin Fear and Greed Index sank to 30, which reads as fear and is its lowest since Aug. 14.
Not everything fell. THORChain's RUNE jumped 13%, which fits an old pattern: when a centralized venue stumbles, traders go looking for places that don't hold their coins for them.
A note on scope. The spillover I can document stays inside crypto. Nobody has shown a clean line from this hack to equities yet, and I'd distrust anyone who draws one this early.
Aave Paused, Checked, and Reopened Within a Day
The most interesting market decision came from a lending protocol, not an exchange. Aave paused new deposits and borrowing across its V3 and V4 markets as a precaution, while leaving withdrawals and repayments open. Its contracts were never touched. The worry was stray collateral and unknown flows, not a bug.
The pause lasted roughly a day. On Friday, Aave said new activity had resumed across every V3 and V4 market, and founder Stani Kulechov said all positions remained overcollateralized.
I like that sequence. A protocol saw a systemic shock, stopped the part that could be gamed, kept the exits open, and reopened once it had checked. Centralized exchanges rarely get to work in that order, since their exits are exactly what they have to close.
Binance Says It Can Cover the Loss
Binance suspended deposits and withdrawals while it ran security checks, and it pledged to cover all losses. The arithmetic behind that pledge matters most to anyone holding assets there.
Binance's stated reserve for making users whole is north of $6.34 billion in company money. Roughly $5 billion of it was already held in the very tokens that got drained. The remainder is being acquired through over‑the‑counter trades and open‑market buying, and Binance cautioned that shallow liquidity and sluggish OTC settlement could drag out some of those purchases. Co‑CEO Yi He said the exchange is buying altcoins in amounts that match what was taken, and that its SAFU fund and corporate holdings include large amounts of Bitcoin and Ether.
Then there's the frozen pile. Binance's verified figure rose from $2.54 billion to about $3 billion, and it says the number could keep growing as investigators trace more. The list of frozen assets reads like a stablecoin shelf: USDT, USDC, Ripple's RLUSD, World Liberty's USD1, StraitsX's XUSD, plus wrapped ETH staking tokens, gold tokens and ARB. Issuers can freeze their own tokens. That's a quiet advantage of the dollar‑pegged kind, and it's probably why $3 billion is stuck rather than gone.
Two caveats. The $5 billion in matching tokens sits in Binance custody, the company wouldn't share wallet addresses, and it hasn't said when it acquired them. And the set‑aside excludes the frozen assets, so the cover figure and the recovery figure shouldn't be added together.
For scale, Binance holds about $134 billion in total assets by DefiLlama's count. A $6.3 billion hole is survivable on those terms. It's also about 4.7% of the whole balance sheet, which is hard to call a rounding error.
EIP‑7702 Handed the Attacker a Shortcut
This is the part that should keep Ethereum developers up tonight, so I'll spend some time on it.
According to co‑CEO Richard Teng, the intruder got control of a hot wallet by setting up an EIP‑7702 delegation, and that setup bypassed the exchange's usual sign‑off process. In his words, it "did not pass through our normal approval controls." EIP‑7702 is the upgrade that lets an ordinary Ethereum account temporarily act like a smart contract wallet. It was built for convenience: batched transactions, sponsored gas, smarter permissions. Here it appears to have given an intruder a handy lever.
How much blame the upgrade deserves is contested. Blockaid CEO Ido Ben‑Natan told Cointelegraph that attackers could have drained the funds without it, since compromised signing systems were the likely root problem. But he said 7702 gave them "a way to do this in one sweep," where otherwise they'd have needed multiple transactions. Fewer transactions means fewer chances for a monitoring system to notice something odd. Ambire CEO Ivo Georgiev agreed the money could have left by other routes. He also raised a warning I find more worrying than the original theft: engineers who regain control of compromised systems can forget to revoke a malicious delegation. Win your keys back and the attacker may still hold a door.
My read, and it's only a read: the 7702 angle is a real lesson but a convenient headline. The harder fact is that Binance first pointed to an engineer's laptop, then said investigators found additional breach points. Teng added that the attacker ran a "self‑destruct mechanism" to erase its tooling and footprints, which slows the forensic work and leaves the final story less certain. A laptop compromise leading to a signing system leading to a delegation nobody approved is a chain of failures, and one bad EIP doesn't explain it.
Cybersecurity analysts suspect North Korea's TraderTraitor group. That attribution comes from analysts, not a government, and Binance hasn't formally confirmed it. If it holds, it fits the group's record of going after the people who hold the keys rather than the code that guards them.
Recovery Hinges on Two Dates
Binance says law enforcement is helping it try to claw back the frozen funds. As Cointelegraph noted, a source said the FBI is involved, though Binance's own post didn't name agencies and the bureau hadn't replied when asked. There's precedent for big recoveries: in February 2022 the Justice Department announced the seizure of 94,000 BTC, worth $3.6 billion then, tied to the 2016 Bitfinex hack. That took years.
The nearer‑term calendar is tighter, and the live updates lay it out. Binance says deposits are working normally. Teng said the goal is to restore withdrawals within 40 hours, ahead of a Sunday deadline, with an initial reserves snapshot before a full proof‑of‑reserves report on Monday. Binance also says it files weekly company‑fund reports with Abu Dhabi's Financial Services Regulatory Authority, a requirement that predated the hack.
If you have coins on the exchange, those two events are your test. A withdrawal window that slips is a bad sign. A reserves report that matches the story is the best news the company can give.
Three Things Will Tell Us How This Ends
First, whether withdrawals actually reopen by Sunday, and whether the outflow rate, already about $6 billion in a day, spikes when they do. Second, whether Monday's report shows the replacement purchases complete, given the warning about thin liquidity. Third, whether the frozen total climbs past $3 billion or the attackers have already moved the rest out of reach.
I'd also watch the 7702 follow‑up. My guess is Binance gets through the week, since the numbers say it can. Whether the industry learns anything is the open question. If exchanges and wallet teams start auditing for lingering delegations now, this will have taught us something. If they don't, I expect the next one to arrive with the same door open.






