The Ledger
Ethereum Bots Empty a 6969-Key Wallet in 12 Seconds
Austin Griffith sent about $1 in ETH to an Ethereum wallet protected by the private key 6969 and saw three pending transactions race to take it. Unchained’s on-chain review found the funds moved out 12 seconds after they arrived, while a 12-digit test wallet had not yet been drained.

A wallet protected by the key 6969 lost its test deposit 12 seconds after the ETH arrived. A separate 12-digit-key wallet had not yet been drained, leaving Austin Griffith’s experiment with a sharp divide between keys bots found immediately and longer ones still holding funds. Griffith, identified by Unchained as Builder Enablement at the Ethereum Foundation, put about $1 into the first wallet on October 21.
“As soon as the dollar landed, there were three transactions in the mempool pending trying to steal it,” Griffith said on Unchained’s Uneasy Money podcast. The episode’s discussion followed news of weak private keys at certificate authority eMudhra, but Griffith’s demonstration tested Ethereum wallets directly: what happens when a small, guessable number controls an address holding funds.
Three transactions raced for 6969
Unchained’s review of Ethereum records found that 0.0004 ETH, worth about $1, reached the address at 20:35 UTC on October 21. A transaction signed with the same key moved the funds out in the next block, 12 seconds later, with most of the deposit spent on network fees. Transactions from three other addresses reached the wallet shortly afterward; two failed.
The deposit came from slop.atg.eth, which had received funds from austingriffith.eth. The test illustrates a basic weakness: a private key is not protected by the wallet interface or its public address. Anyone who can identify the key can sign transactions for that wallet, and a key chosen as a small number is easy to search.
Short keys had already left a trail
Griffith said every number below 256 already had a nonce, Ethereum’s counter of transactions sent by an address. Unchained checked the mainnet addresses associated with keys 1 through 255 and found that all 255 had sent transactions. That observation points to prior activity across the entire tested range, though the records alone do not identify who controlled the addresses or how each key was found.
Griffith initially estimated that bots might stop finding keys somewhere between eight and 12 digits. During the episode, he said a 10-digit key had been drained “right away,” while a 12-digit key had “not yet” been drained. He also said he had funded 14- and 16-digit keys to test the limit.
The longer-key results remain incomplete
Unchained’s on-chain review found four additional addresses funded about 14 minutes after the first deposit. One was emptied within 12 seconds, while three still held funds as of October 23. Griffith did not identify which key length belonged to each address, so the records could not confirm the status of the 14- and 16-digit tests.
The distinction matters: the reported results show specific test wallets being targeted, not a measured boundary for what Ethereum bots can crack. The episode’s hosts said they would check the longer-key wallets the following week. At the time of Unchained’s review, the 12-digit test remained undrained, while one shorter-key test had been emptied in a single block interval.
Sources
- Original source Unchained · Austin griffith demonstrates how fast bots can drain weak e… unchainedcrypto.com
Other pages read
- Unchained · Uneasy money is the internet breaking because bots never ge… unchainedcrypto.com
- Yahoo Tech (syndicated) tech.yahoo.com
Related stories
- Polkadot Warns Fearless Users After Browser Extension Leaks Keys
- Ethereum Draft Seeks Reproducible Transaction Simulations
- Ethereum Draft Defines Risk Reports for AI-Signed Transactions
- Electrum 4.8.3 Patches Bitcoin Wallet Transaction-Spoofing Flaw
- Qubic Restarts Network and Opens Claims After 1,404-Wallet Drain