Zimbuck – Your Market. Your Community.

Keplr Wallet Hit by Web3Auth Incident: Social-Login Accounts Drained, Seed-Phrase Wallets Said to Be Unaffected

5 min read
0
Comments
476
Views

Keplr, the main wallet for the Cosmos ecosystem, has paused Google and Apple logins after users reported unauthorised transfers — and the problem appears to sit with its authentication provider, Web3Auth, not with Keplr's own code. The incident, disclosed on November 7, is a live lesson in a risk most wallet users never think about, and it is being tracked on the Zimbuck News page.

Keplr's initial assessment draws a sharp line: accounts created with a recovery phrase or a hardware wallet are not affected, while some accounts created through Google or Apple social login are. If you use Keplr, which group you are in decides what you should do today — the safety steps are collected for discussion in the Zimbuck Market News group.

What happened, and when

  • November 6, 23:13: Web3Auth posts its first notice of a security issue and pauses its embedded wallet service as a precaution
  • November 7, 06:38: Keplr confirms reports of unauthorised transactions in some Google/Apple-login accounts and pauses those login methods
  • November 7, later: Chainapsis co-founder Josh Lee says the incident originated at Web3Auth, the provider Keplr uses, and puts the early estimate at about 20% of Google/Apple-login accounts potentially exposed — with only a fraction of that group appearing to have been exploited
  • Community investigators reported stolen assets involving Injective, Osmosis and Cosmos Hub, with initial loss estimates above $700,000 and independent tracking suggesting larger outflows — Keplr has not confirmed any official loss total

Keplr wallet Web3Auth incident

Why social login is the weak point here

Social login exists to make wallets feel like normal apps: sign in with Google or Apple instead of writing down 12 or 24 words. Under the hood, a provider like Web3Auth splits and reconstructs the wallet's key material when you sign in. That convenience creates a centralised point of failure — if the provider's service is compromised, the attacker does not need your phone, your password, or your recovery phrase.

That is the opposite failure mode from the one in our recent CertiK DarkSword warning, where the phone's operating system itself was the target. Here, the device can be perfectly secure and the wallet app unpatched in no way — the trust placed in a third-party login layer is what failed. It is also different from a classic exchange hack: no exchange was breached, and seed-phrase and hardware-wallet accounts are, on Keplr's initial assessment, untouched.

What Keplr users should do now

Keplr's guidance for affected social-login users is specific:

  • Do not add funds to a Google/Apple-login Keplr account while the investigation continues
  • Do not re-import or recreate those accounts in other apps — moving the same key material does not remove the exposure
  • Ignore unsolicited "recovery" help, support messages and links claiming to restore stolen funds — breach headlines always attract a second wave of scams, a pattern we covered in our explainer on how crypto rewards and wallet mechanics really work
  • If you hold a significant balance in an affected account type, wait for Keplr/Web3Auth's official migration guidance rather than improvising

Web3Auth, which was acquired by MetaMask developer Consensys in 2025, said its initial investigation found no evidence that MetaMask users were impacted. No reimbursement plan and no timeline for restoring social login has been announced. The detailed incident round-up is available from Crypto Adventure's Keplr incident report.

Wallet security lesson

The wider lesson for every wallet user

Every login method is a trade-off. A recovery phrase puts the whole burden on you — lose it or leak it and the funds are gone — but no company in the middle can be breached into your wallet. A hardware wallet keeps keys offline entirely. Social login removes the burden and adds a counterparty. None of these is "wrong", but the Keplr incident shows the counterparty risk is real, priced in neither by most users nor, apparently, by the "not your keys" debate, which usually assumes the choice is only between an exchange and self-custody.

Until a full technical post-mortem is published, the root cause and the final losses remain unconfirmed — treat any precise total circulating on social media as unverified. What is confirmed is enough to act on: pause, do not deposit, and wait for the official migration path.

FAQ

Is my Keplr wallet affected?
On Keplr's initial assessment, only some accounts created with Google or Apple login are affected. Accounts created with a recovery phrase or used with a hardware wallet are not affected.

How much was stolen?
Initial community estimates exceeded $700,000, with some tracking suggesting more, but Keplr has not confirmed an official loss total and the investigation is ongoing.

Should I move my funds right now?
Keplr advises social-login users not to add funds and not to re-import or recreate the affected accounts elsewhere. Follow Keplr and Web3Auth's official channels for the migration steps rather than acting on social-media advice.

Discuss wallet security with other traders on Zimbuck — join the conversation on the finance social platform for traders and investors. This article is market news and general information only, not financial advice.