Topic
blockchain
Exchange and wallet incidents read from the chain itself: transactions, account code, token freezes, and what they do and do not prove.
5 engineering notes.
- Binance's RCA: access path disclosed, signing approval unexplainedUpdated Binance's 3 November report traces the attack from a fake job interview to its wallet signing service. The reproduced Ethereum delegation matches it; why the signing service signed 50 EIP-7702 authorizations is still unexplained.
- Binance, missing crypto and a permission that stayedExplained to kidsA paper-points activity explains the Binance incident, lasting digital permissions and why frozen funds are not the same as returned funds.
- Binance reports $6.3bn impact; cause remains preliminaryTen-network outflows, frozen assets and company-funded cover measure different things; Ethereum revocation is confirmed, but the intrusion route and live service status remain unresolved.
- Binance 14 cleared its EIP-7702 delegation: what the chain proves, and what it does notAt block 26,301,896 the address labelled Binance 14 reset its code to empty with a type-4 transaction. The clear removes the sweeper contract; it does not prove the signing key is safe. A read-only probe for any delegated account.
- Binance's $3.3B wallet transfers: what the chain shows, and how to tell a hack from a moveRead from a public Ethereum node: an EIP-7702 delegation on the Binance 14 address, a 65-token sweep, and Tether and Circle freezes. Signs that separate theft from an internal move.
Related service: Security & Penetration Testing →