BTC$60,984 +1.58%ETH$1,716 +2.29%SOL$70.20 +0.17%XRP$0.92304 -0.33%BNB$556.17 +1.64%DOGE$0.05509 +0.21%ADA$0.14405 -0.05%TON$0.97663 +2.72%

Keplr Halts Google and Apple Logins After Web3Auth Flaw Exposes Keys

Keplr suspended social login wallets after a flaw in Web3Auth's infrastructure exposed private keys. Seed-phrase and hardware wallet users are not affected.

By · · 3 min read
Keplr Halts Google and Apple Logins After Web3Auth Flaw Exposes Keys

Key takeaways

  • Keplr paused Google and Apple sign-in on November 6 after users reported unauthorized transactions.
  • Web3Auth, which generates keys for those accounts, traced the incident to a flaw in its own infrastructure.
  • Wallets created with a seed phrase or linked to a hardware wallet are not affected, according to Keplr.

Keplr, one of the most widely used wallets in the Cosmos ecosystem, has suspended its Google and Apple login options after users reported funds leaving their accounts without permission. The wallet's social login accounts rely on Web3Auth, a third-party key-management service, which has confirmed a security incident on its side.

Keplr disabled the feature on November 6. The same day, Web3Auth acknowledged an incident affecting services used by some of its partners, and on November 7 it attributed the problem to a flaw in its own infrastructure that exposed private keys. Keplr has said the vulnerability is not in its app's code. Neither company has yet explained exactly how the attackers exploited the flaw.

Who is affected

The risk is limited to users who created a Keplr wallet by signing in with Google or Apple, because Web3Auth generates the private keys for those accounts. Keplr co-founder Josh Lee estimated that around 20% of social login accounts could be exposed, though only a portion were actually drained. There is no confirmed figure for total losses yet.

Community investigators have traced suspicious transfers involving Injective, Osmosis and Cosmos Hub tokens, although neither company has published an official list of affected networks. Web3Auth, which has been owned by MetaMask developer Consensys since 2025, said it has found no sign that MetaMask users are affected.

According to Keplr's preliminary review, wallets created with the user's own recovery phrase and wallets linked to a hardware device are not affected.

Rescue moves can look like theft

Web3Auth has temporarily suspended its embedded wallet service. Together with its partners, it moved funds out of at-risk accounts that had not yet been attacked, using the same access route as the attacker, to keep them safe. That means some users may see an empty balance even though their funds were rescued rather than stolen. Web3Auth says it is compiling a verified list of destination addresses so users can tell the difference, and Keplr is building a tool to check whether an account was affected. Staked or locked balances are making the recovery slower.

Why it matters

Social login is one of the main ways the industry tries to make crypto feel as simple as a regular app. This incident shows the trade-off: when a third party manages key generation, a single infrastructure flaw can put many users at risk at once, regardless of how careful each person is.

What users should do

  • Do not deposit new funds or staking rewards into Google or Apple login accounts until Keplr restores the service.
  • Move any freely available tokens to a new wallet secured by your own recovery phrase, as Keplr advises.
  • Do not import the social login account into another app while the investigation continues.
  • Ignore unsolicited recovery offers, and never share a recovery phrase or private key.
  • If a balance shows as empty, check the destination address against Web3Auth's official list before assuming theft.

No refund plan or date for restoring social login has been announced yet. Updates are being posted on Keplr's official X account.

ATOMOSMOINJ#keplr#web3auth#wallet hack#cosmos#security
Sources: CryptoTicker

This article is for informational purposes only and does not constitute financial advice. See our editorial policy and disclaimer.

Found this useful? Tell us how we are doing.