Without Chainwall · EIP-7702 leaked-key drain, modelled on Binance, Oct 2026

The left is a stand-in exchange portfolio. Press Launch attack and watch it react while the panel on the right shows what the attacker is doing. Everything runs on Whitechain Testnet with test tokens.

Ready · test tokens only

Estimated balance

—tUSD

≈ —

Change this session —

Balance, this session

Exchange hot walletNormal wallet

Assets

Coin	Amount	Price	Value	Allocation
tUSD Test USD	—	$1.00test token	—	0%
ETH Ethereum	—	—gas only	—	0%

Recent transactions

this session

No transactions this session. Deposit test tokens or launch the attack.

How the drain works

four moves, no owner approval

The attacker never asks the owner for anything. Open any move to see what it does and the real proof behind it.

Each EIP-7702 authorization says “let this wallet run the attacker’s contract.” They’re signed offline with the leaked key, so nothing shows up on-chain or in the owner’s app yet. This is the step the portfolio on the left cannot see.
The 50 signatures appear here when the run starts.

This run, in numbers

Filled in live from the chain.

Approvals asked of the owner: —
Gas paid by the owner: —
Authorizations signed: —
Transactions sent: —
Moved to the attacker: —
Time from Launch: —

Live transaction log

Every line is a real step on Whitechain Testnet, with its transaction hash. This is the proof behind the animation above.

Live logempty

$ binonce attack --chain whitechain-testnet

Waiting for the chain. See the setup note above.

Saved to Arkiv

Every run, and every sweeper contract it uses, is written to a public registry on Arkiv so anyone can check a contract before trusting it.

Arkiv

Couldn’t reach Arkiv. Try refreshing.