Web3Auth Security Issue Forces Keplr Wallet to Suspend Google and Apple Logins After Private Key Exposure

A security flaw in the systems of authentication provider Web3Auth compelled the Cosmos focused wallet Keplr to disable Google and Apple sign-in options after private keys for certain accounts became accessible to unauthorized parties.

The exposure prompted a wave of unexpected fund movements across multiple networks, as blockchain analysts later documented transfers totaling more than six million dollars.

Subsequent protective steps taken by Web3Auth itself have made it difficult to determine how much of that sum was actually taken by malicious actors versus relocated for safekeeping.

Keplr has long offered users the convenience of creating wallets through ordinary social accounts rather than generating and safeguarding a recovery phrase. That convenience depends on Web3Auth, which generates and manages the underlying key material for those accounts.

On November 6, 2026, Web3Auth identified a security issue affecting its infrastructure and temporarily paused its embedded-wallet service.

Early the following morning, Keplr reported receiving notices of unauthorized transactions on some wallets created with Google or Apple logins.

The wallet provider immediately suspended those login methods, advised users against depositing additional funds or re-importing the affected accounts, and began joint investigation with Web3Auth.

Only wallets that relied on the social-login pathway appear to have been at risk.

Accounts established with a conventional recovery phrase or protected by a hardware device remained outside the scope of the incident, according to Keplr’s assessments.

Company co-founder Josh Lee estimated that roughly one-fifth of Keplr’s Google and Apple login accounts may have been touched by the vulnerability, though only a smaller portion of those had been actively exploited at the time of his statement.

On-chain researchers, notably the analytics firm Bitquery, examined activity across Cosmos Hub, Osmosis, Injective and several other networks.

They identified more than 44,000 wallets that experienced outgoing transfers during the November 6–7 window, with the aggregate value of those movements exceeding six million dollars.

Much of the activity involved Cosmos Hub tokens, including substantial quantities of staked ATOM that were moved without observing the usual unbonding delay.

Web3Auth has stated that a significant share of the observed transfers formed part of its own emergency response.

The company described initiating white-hat recovery operations that targeted vulnerable but not-yet-compromised wallets, using the same technical pathway the original attacker had employed.

By November 8 it published a list of recovery addresses under its control and noted that some of the protective movements had been mistaken for theft.

Independent reviews of those addresses later showed holdings of approximately 5.6 million dollars.

Web3Auth has said the recovered assets are secure and that it is coordinating with Keplr on a process to return them to legitimate owners.

Neither party has released a final figure for irreversible losses attributable solely to the attacker.

Affected users have been instructed to avoid sending new funds to the original social-login accounts and to transfer any remaining liquid balances to wallets controlled by recovery phrases or hardware devices.

Both organizations have warned against responding to unsolicited messages or links offering assistance, emphasizing that official updates will appear only on their verified channels.

Staked or locked positions have added operational complexity and will require additional time to resolve.

The episode underscores the concentrated risk that can arise when large numbers of self-custody wallets depend on a single third-party key-management service.

While the social-login model lowers the barrier for new users, a single infrastructure defect can simultaneously expose thousands of accounts. Keplr has emphasized that the vulnerability originated in Web3Auth’s systems rather than in its own code base, and recovery efforts remain ongoing.



Sponsored Links by DQ Promote

 

 

Disclosure Quest

Reg A - Form 1-A Filings Beta

Beta. Initial Form 1-A only. Target raise is the stated Amount to be Raised, totaled. Compared with the same dates one year earlier.

YTD: Jan 1, 2026 - Nov 17, 2026 vs Jan 1, 2025 - Nov 17, 2025

Share this graph
Number of Filings137Prior 131 +4.6%
Target Raise, Total$3.48BPrior $3.62B -3.7%
This YTDYear priorChange
Filings 137 131 +4.6%
Target raise $3.48B $3.62B -3.7%

Sponsored by the Crowded Media Group the leading digital news service covering the global Fintech Industry, including digital assets, crowdfunding, tokenization, and other innovations in capital markets. email us @CrowdfundInside

Source: DisclosureQuest. Initial Form 1-A only.

Created by Crowded Media Group

This display counts initial Form 1-A filings only. It does not represent subsequent filings, including Form 1-A/A amendments or Form 1-A POS post-qualification updates filed by the issuer. Amounts are the stated Amount to be Raised on the initial filing, not capital raised and not amounts revised in later filings.

0 0 votes
Article Rating
Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Newest
Oldest Most Voted
 
0
Would love your thoughts, please comment.x
()
x
Send this to a friend