Keplr pauses Google and Apple login after Web3Auth flaw exposes some wallet keys; recovery under way
Cosmos wallet Keplr paused Google and Apple sign-up and sign-in after users reported unauthorized transactions. Keplr blamed a Web3Auth infrastructure vulnerability that exposed some social-login wallet keys; recovery is under way, while recovery-phrase and hardware wallets are unaffected.

Table of Contents
Keplr pauses social login
Keplr, a widely used wallet for the Cosmos ecosystem, has paused sign-up and sign-in with Google and Apple accounts after some users reported transactions they had not approved. In a post on X at 04:38 UTC on November 7, 2026, Keplr said it had received reports of unauthorized transactions on some accounts created with Google or Apple login, had flagged them to Web3Auth and was investigating with that team.
Web3Auth, the wallet-login provider that Keplr uses for these social-login accounts, had posted on X at 21:13 UTC on November 6 that it was aware of a security issue affecting its services used by some third parties. It said it had temporarily paused its embedded wallet service and had found no evidence that MetaMask users were affected. Crypto.news and Coindaro describe Web3Auth as owned by Consensys, the company behind MetaMask.
Web3Auth identifies an infrastructure issue
At 16:53 UTC on November 7, Web3Auth said it had identified a security issue in its infrastructure affecting certain embedded wallets used by Keplr. Keplr's update at 17:17 UTC that day described the cause as a Web3Auth infrastructure vulnerability that led to a private-key breach for some users who signed in with Google or Apple. Keplr said that wallets created with a recovery phrase or a hardware wallet are not affected.
Some outflows were recovery operations
Some of the outflows seen on-chain were not the attacker's. Web3Auth said at 17:06 UTC on November 7 that, together with partners, it had started “whitehat recovery activities targeting vulnerable but not yet impacted wallets utilizing the same path of the original attacker.” In other words, a rescue operation used the same route to move funds out of exposed wallets. Keplr said some Google and Apple accounts may therefore show a reduced or empty balance. An empty balance on its own does not show whether funds were taken by the attacker or moved for safekeeping.
Verified recovery addresses
On November 8, at 06:23 UTC, Web3Auth published a list of what it called verified recovery addresses, used to secure affected assets and not controlled by the attacker. The list covers Cosmos Hub, Osmosis, Celestia, Akash, Noble, Injective, dYdX, Babylon, Axelar, Saga and Agoric, plus one EVM address that Web3Auth says is used on eight chains. Keplr reposted the list at 06:31 UTC. Web3Auth said the list would be updated as more addresses are verified.
Reported scope and uncertainty
Neither Keplr nor Web3Auth had published an official count of affected wallets, a loss figure or a technical explanation of the flaw at the time of writing. Keplr co-founder Josh Lee estimated that about 20% of accounts created with Google or Apple login were affected, but said only a fraction of those appeared to have actually been exploited, according to reports by Altcoin Reporter and Crypto.news. Blockchain data firm Bitquery traced about $6.01 million moving from more than 44,000 wallets to two collection addresses, according to Crypto.news. That on-chain figure is Bitquery's estimate, not a confirmed loss, and it may include transfers made by the recovery operation.
Keplr's advice to affected users
Keplr's current advice to users who created a wallet with Google or Apple login is not to send new funds to that account, to move any remaining liquid assets to an account secured by a recovery phrase or a hardware wallet, to trust updates only from the official Keplr and Web3Auth accounts on X, and to ignore direct messages or links offering “recovery.” Keplr said staked and locked assets take longer to handle, and that it is working with Web3Auth on a way for users to check whether their accounts were affected. Google and Apple login remained paused when this article was written.
What social-login wallets rely on
The incident is a reminder that social-login wallets trade some of the work of managing a recovery phrase for reliance on a third-party key-management provider. This article is news, not security or investment advice.
Timeline
Event, publication and writing times: The first Web3Auth notice was posted at 21:13 UTC on November 6, 2026, and Keplr's first notice at 04:38 UTC on November 7, 2026. The latest official update used here was posted at 06:23 UTC on November 8, 2026. This article was written on November 8, 2026, around 09:00 UTC.
Image caption: AI-generated illustration of a phone wallet with a security warning. It is not a photo of the incident or of the Keplr app. Framed by MyTraderBot.
Sources & further reading
- Keplr on X: first notice of unauthorized transactions (7 Nov 2026, 04:38 UTC)
- Keplr on X: “What this means for Keplr users” (7 Nov 2026, 17:17 UTC)
- Keplr on X: verified recovery addresses (8 Nov 2026, 06:31 UTC)
- Web3Auth on X: security issue, embedded wallet service paused (6 Nov 2026, 21:13 UTC)
- Web3Auth on X: issue identified in infrastructure used by Keplr (7 Nov 2026, 16:53 UTC)
- Web3Auth on X: white-hat recovery activities (7 Nov 2026, 17:06 UTC)
- Web3Auth on X: update on Keplr asset recovery and verified recovery addresses (8 Nov 2026, 06:23 UTC)
- Crypto.news: Keplr halts Google, Apple logins as $6M wallet drain hits Cosmos (8 Nov 2026)
- The Defiant: Keplr pauses Google and Apple login after unauthorized transaction reports (7 Nov 2026)
- Altcoin Reporter: Keplr pauses social login after unauthorized transactions tied to Web3Auth (Nov 2026)
- Coindaro: Keplr wallet, Web3Auth flaw exposed Google and Apple login keys (updated 8 Nov 2026)
See the signals and their results
Browse publicly logged signals and how they performed, or create a free account to follow them.





