The Ledger
Attacker Takes at Least $6.0M From 44,000+ Keplr Wallets Across Eight Cosmos Chains
An attacker drained Keplr wallets using Google or Apple login across eight Cosmos chains, with collector addresses holding $6.01 million. The drain continued after Keplr warned users, and the attacker moved staked ATOM without waiting for the usual unbonding period.

An attacker took at least $6.0 million from Keplr wallets across eight Cosmos chains during an 18-hour drain on 6 and 7 November 2026. Bitquery counted at least 44,041 wallets on seven Cosmos chains and 7,603 on Injective sending funds to two collector addresses, which held $6.01 million at the time of the investigation. Neither address had sent a transaction, while the Cosmos Hub drain was still running at 15:38 UTC on 7 November.
Keplr’s warning followed the first sweeps
The affected wallets had been opened with Google or Apple login. Keplr confirmed unauthorized transactions in those accounts at 04:38 UTC on 7 November, said wallets backed up with recovery phrases and hardware wallets were not affected, and paused Google and Apple login. Web3Auth, the service behind that login, had reported a security issue and paused its embedded wallet service at 21:13 UTC on 6 November.
The first sweep Bitquery identified occurred at 20:52 UTC on 6 November. Within seconds, 10 Cosmos Hub wallets each sent the attacker an amount worth less than two cents, which the investigation says looked like a test. The first wave then reached Cosmos Hub, Osmosis, Celestia and Akash before midnight.
Bitquery counted 86% of victims on the seven same-key chains as having lost funds after Keplr’s warning. The largest wave began about two hours after the warning and was six times the size of the first. Pausing social login did not protect users whose keys the attacker already held. On the linked Cosmos chains, one key can open an address on every chain a user has used, enabling funds to be swept from several chains.
Funds and losses across the chains
Cosmos Hub held $3.50 million of the stolen funds, followed by Osmosis at $1.04 million and Injective at $615,000. Bitquery also listed $422,000 on Akash, $238,000 on Celestia, $108,000 on Noble, $62,000 on dYdX and $16,000 on Babylon. The dollar figures use spot prices at 15:27 UTC on 7 November. Tokens without market prices and 45,000 likely spam USDC on Cosmos Hub were excluded, so the totals are floors.
The seven chains that share the collector key accounted for 44,041 wallets. Injective uses a different address format; Bitquery identified 7,603 wallets there and estimated that between 440 and 934 of them were additional victims beyond those on the other chains. The estimate came from checking a sample of 299 victims. Many people lost funds on more than one chain: 46% of drained wallets on the seven same-key chains were affected on at least two.
Most individual losses were small, but the larger losses made up much of the total. The typical wallet lost $1.34, and 88% lost less than $100. Three wallets lost at least $100,000, with the largest single loss at $325,000. Bitquery found that 47% of the wallets lost less than a dollar, while wallets losing $1,000 to $10,000 accounted for a third of the dollars taken.
Staked ATOM left without the 21-day wait
Bitquery traced 1.96 million staked ATOM moved as share tokens, alongside 0.35 million ATOM sent from victims’ balances and 0.18 million ATOM in staking rewards paid to the attacker. In the bundled transactions, the attacker first changed victims’ reward addresses, then converted their stakes into share tokens and sent those tokens to a collector address. A separate gas wallet paid transaction fees.
The process let the stake leave victims’ wallets without the normal 21-day unbonding wait. However, the share tokens are not immediately equivalent to liquid ATOM: turning them back into ATOM still requires waiting 21 days or using a liquid-staking deposit. Bitquery said the attacker had not done either. The change to reward addresses also directed about $251,000 in staking rewards to the attacker.
From 09:57 UTC on 7 November, the attacker used bundles that could include up to six wallets. Sweeps on seven chains stopped within the same 19 seconds, around 10:34 UTC. Cosmos Hub was the exception: the drain there continued into the afternoon.
Funds that may still be stopped
Bitquery identified 81,006 USDC on Noble, which Circle can block. The investigation also traced funding for the attacker’s gas wallet to two outside wallets. They sent 73.29 ATOM, 45.70 ATOM and 109.62 ATOM on 7 November. Bitquery described the senders as resembling exchange payout wallets but said it could not confirm who operated them. If either is associated with an exchange, the exchange may be able to identify the account that requested the withdrawals.
Bitquery’s figures cover transfers through 15:38 UTC on 7 November, while the Cosmos Hub drain was still running. Keplr’s advice to affected users was not to send new funds to social-login accounts or import them elsewhere; any new funds should go into a new wallet with its own recovery phrase.
Sources
- Original source Bitquery bitquery.io
Related stories
- Predict.fun Wallet Drains Hit $398,000 Across 29 Accounts
- NGRAVE Phishing Attack Drains $2.65M From 84 Wallets
- Qubic Halts Network After 1,404 Wallets Lose 2.94T QU
- Draft Multisig Session Protocol would let remote Bitcoin cosigners set up wallets without a coordinator
- Unocoin Says BitGo Wallet Backup May Have Been Exploited