DeFi Intel

Keplr Pauses Google and Apple Login After Unauthorized Transaction Reports

The wallet says recovery-phrase and hardware-wallet accounts are unaffected in its initial assessment, while social-login users should stop sending funds to their accounts.

TL;DR

Keplr stopped Google and Apple login on Nov 7, 2026 after users reported unauthorized transactions linked to a Web3Auth security flaw. About 20 % of social‑login accounts may be affected, while recovery‑phrase and hardware‑wallet accounts stay safe, prompting a broader warning about third‑party login services.

Key facts

  • Keplr paused Google and Apple login on November 7, 2026.
  • Unauthorized transactions were reported on accounts created via those social logins.
  • The issue is tied to a security incident at Web3Auth.

Keplr, the non‑custodial wallet that serves as a primary gateway to the Cosmos ecosystem, halted its Google and Apple social‑login options on November 7, 2026 after users reported unauthorized transactions on accounts created through those services. The incident is linked to a security problem at Web3Auth, the third‑party provider that powers Keplr’s social‑login feature. Keplr’s co‑founder Josh Lee clarified that wallets generated with a recovery phrase or hardware device remain safe, while roughly one‑fifth of social‑login accounts may be exposed.

Background

Keplr operates as a non‑custodial wallet, meaning private keys that authorize transactions are held by users rather than the company. It is widely used across Cosmos, a network of independent blockchains that interoperate via the Inter‑Blockchain Communication (IBC) protocol. To simplify onboarding, Keplr offers social logins that let users create wallets using existing Google or Apple accounts, bypassing the need to write down a seed phrase. These social logins rely on Web3Auth, a ConsenSys‑owned service that generates private keys through Distributed Key Generation (DKG), a process that splits key creation among multiple parties so no single entity holds the full key. On November 6, 2026 Web3Auth posted on X that it had detected a security issue affecting services used by some third parties and temporarily paused its embedded wallet service. The company later indicated no evidence of impact on MetaMask users and promised to share further details once available. Keplr responded the next day, confirming reports of unauthorized transactions on accounts created with Google or Apple login, and advised users to stop sending funds to those accounts while the investigation proceeds. The co‑founder of Chainapsis, the developer behind Keplr, reiterated that the problem originates from Web3Auth, not Keplr’s own code, and estimated that about 20 % of social‑login accounts could be affected, though only a fraction appear to have been fully exploited.

What happened

On November 6, 2026 Web3Auth announced on X that it was aware of a security issue affecting services used by some third parties and that it had paused its embedded wallet service (Source 1). The next morning, around 04:38 UTC on November 7, Keplr issued a statement quoting Web3Auth’s earlier post and confirming that it had received reports of unauthorized transactions on Keplr accounts created with Google or Apple login (Source 1). Keplr’s support documentation explains that Google login accounts obtain their private keys from Web3Auth via Distributed Key Generation, a method designed to prevent any single party from holding the full key (Source 1). The wallet’s co‑founder Josh Lee posted on X at about 08:29 UTC on November 7, stating that the incident was not a hack of Keplr’s own code but originated at Web3Auth, and that roughly 20 % of social‑login accounts might be affected, with only some fully exploited so far (Source 1). Keplr advised holders of potentially affected accounts to stop sending new funds, avoid re‑importing those accounts elsewhere, trust only updates from Keplr’s official X account, and ignore unsolicited recovery offers (Source 1). The company also paused Google and Apple login functionality while it works with Web3Auth and MetaMask to track affected accounts and recover funds (Source 1). Web3Auth’s status page listed its Login Service as under maintenance due to the security incident, and the company said it had found no evidence that MetaMask users were impacted (Source 1). Other outlets repeated the core facts, noting the pause of social logins, the link to Web3Auth, and the estimate that about one‑fifth of such accounts could be at risk (Source 3).

Market impact

The sources do not provide specific price movements, trading volumes, or monetary loss figures related to the Keplr incident. No quantitative data on token flows or market capitalization changes is disclosed. The only numerical detail is the co‑founder’s estimate that roughly 20 % of Google and Apple login accounts could be affected, and the statement that only a fraction of those appear to have been fully exploited (Source 1, Source 3). No loss amount has been disclosed (Source 3). Consequently, the market impact can be described only in qualitative terms, with the incident prompting heightened caution among Cosmos users and potentially influencing sentiment toward social‑login solutions in the broader DeFi space.

Why it matters

The incident highlights the vulnerability of third‑party authentication services that underpin social‑login features in non‑custodial wallets. Because Keplr is a primary gateway to the Cosmos ecosystem, any compromise could affect a large user base and undermine confidence in streamlined onboarding methods that bypass seed phrases. The reliance on Distributed Key Generation does not appear to have prevented the breach, suggesting that the security flaw may lie in the implementation or operational controls at Web3Auth rather than the cryptographic design itself. Moreover, the fact that recovery‑phrase and hardware‑wallet accounts remain safe underscores the continued importance of traditional key management practices, especially for newer users who may be attracted to the convenience of social logins. The pause of Google and Apple login options also serves as a real‑time risk mitigation step, but it may temporarily disrupt user activity and token transfers on Cosmos, potentially affecting staking and IBC‑related operations. Finally, the collaboration between Keplr, Web3Auth, and MetaMask to track affected accounts signals a coordinated industry response, yet the lack of disclosed loss amounts leaves uncertainty about the financial fallout for individual users.

DeFi Intel’s take

Editorial analysis, not a statement of fact.

DeFi Intel's take: the Keplr pause underscores the trade‑off between user‑friendly onboarding and security in the DeFi stack. While Distributed Key Generation is designed to mitigate single‑point failures, the breach suggests that operational security at the authentication layer remains critical. We read this as a warning that social‑login solutions, though convenient, may expose newer users to heightened risk, especially when third‑party providers are involved. The incident also reinforces the resilience of traditional seed‑phrase and hardware‑wallet approaches, which remain unaffected. As Keplr works with Web3Auth and MetaMask to remediate, the broader Cosmos community may see a short‑term dip in activity, but the episode could drive stronger security standards for embedded wallets across the ecosystem.

Sources used for this analysis

DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.

Frequently asked questions

What caused the unauthorized transactions on Keplr accounts?

The unauthorized transactions are linked to a security issue at Web3Auth, the third‑party service that provides Keplr’s Google and Apple social‑login functionality. Keplr’s co‑founder said the problem originated at Web3Auth, not in Keplr’s own code.

Are wallets created with a recovery phrase or hardware device affected?

No. Keplr confirmed that accounts generated with a recovery (seed) phrase or connected through a hardware wallet are not impacted by the incident and remain secure.

What steps did Keplr advise users of potentially affected accounts to take?

Keplr asked users to stop sending new funds to the affected accounts, avoid re‑importing or recreating those accounts elsewhere, trust only updates from Keplr’s official X account, and ignore any unsolicited recovery offers.

Direct answers

Short answers, written to be quoted.

Why did Keplr pause its Google and Apple login features?
Keplr paused the features because users reported unauthorized transactions on accounts created with those social logins, and the problem was traced to a security incident at Web3Auth.
Which Keplr accounts are safe from the breach?
Accounts created with a recovery phrase or connected through a hardware wallet remain safe and are not affected by the Web3Auth incident.
What percentage of social‑login accounts might be affected?
Keplr’s co‑founder estimated that about 20 % of Google and Apple login accounts could be affected, though only a fraction have been fully exploited.
Read full article on The Defiant →

DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at The Defiant.

Entities in this story

Discussion

Comments are reviewed before publication.

No comments yet.

Want the full article?

Continue reading on The Defiant →

Stay current on entity-tagged crypto news

Get the weekly DeFi Intel brief — entity-graph intelligence covering protocols, tokens and incidents, free to your inbox.