Keplr Pauses Social Logins After Wallet Security Incident
Keplr and Web3Auth responded to an incident affecting some Google and Apple sign-in users while keeping recovery-phrase and hardware wallets outside the reported scope.
Keplr and Web3Auth responded to an incident affecting some Google and Apple sign-in users while keeping recovery-phrase and hardware wallets outside the reported scope. This is an original TLT brief based on reporting by Blockonomi, with live market data added, as of Sun, 08 Nov 2026 16:45:02 UTC.
The incident affects wallets created through social-login infrastructure, potentially exposing funds held in embedded wallets and requiring affected users to avoid sending additional assets until their status is confirmed.
- Google and Apple sign-in accounts were affected across both outlets’ coverage.
- Web3Auth paused its embedded-wallet service while Keplr froze social login.
- Bitquery initially tracked about $6.01 million across eight destinations.
- Keplr says recovery-phrase and hardware-wallet accounts were outside the incident scope.
- Keplr Pauses Social Logins Following Reported Wallet Transfers
- Keplr Pauses Social Logins After Wallet Security Incident — this brief
Keplr users who accessed their wallets through Google or Apple were caught in a security incident involving the social-login infrastructure used by the wallet provider. Both Blockonomi and BeInCrypto report that affected users included people signing in through those two platforms, with Web3Auth confirming that some flagged addresses contained funds it had secured for users. The available reporting does not establish every affected account or the final amount taken from each wallet.
The response included two service restrictions. According to Blockonomi, Web3Auth paused its embedded-wallet service, while Keplr froze its social-login function. Users with potentially affected accounts were instructed not to deposit additional assets, reducing the risk of adding funds while the scope of the incident was being assessed. Keplr also said recovery-phrase and hardware-wallet accounts remained outside the incident’s scope, separating those account types from the affected Google and Apple sign-in pathway.
Bitquery’s initial on-chain analysis, as cited by Blockonomi, tracked approximately $6.01 million moving across eight destinations. That figure represents the activity initially identified by the tracking service rather than a final loss determination, and BeInCrypto does not provide a competing monetary estimate. BeInCrypto’s additional emphasis is that some flagged addresses continued to hold assets Web3Auth had secured on behalf of affected users, making the locations of those funds relevant to the response and recovery process.
The distinction between login methods is central to the reported incident. Google and Apple social sign-ins were affected, whereas Keplr placed recovery-phrase and hardware-wallet accounts outside the reported scope. The involvement of Web3Auth’s embedded-wallet infrastructure indicates that the response targeted more than the Keplr-branded interface alone, although the supplied coverage does not specify the precise technical cause or the number of impacted wallets.
Crypto market conditions were comparatively subdued during the report. The total market capitalization stood at $2.61 trillion, with the overall market described as flat. 
Bitcoin gained 0.39% over 24 hours, while the Fear & Greed index registered 28, corresponding to Fear. No coin was specifically identified as directly involved in the incident, so the next points to monitor are the service status of Web3Auth and Keplr, further identification of affected addresses, and any revision to the initial $6.01 million tracking figure.
Keplr Pauses Social Logins After Wallet Security Incident — questions & answers
Which Keplr users were affected by the incident?
Both Blockonomi and BeInCrypto report that users who signed in with Google or Apple were affected. Keplr says recovery-phrase and hardware-wallet accounts were outside the reported scope.
How much money did Bitquery initially track?
Blockonomi reports that Bitquery initially identified about $6.01 million across eight destinations. The supplied coverage does not provide a final loss figure.
What did Keplr and Web3Auth do after the incident?
Blockonomi reports that Keplr froze social login and Web3Auth paused its embedded-wallet service. Affected users were told not to deposit additional assets.
Which outlets reported this story?
This is an original TLT brief that synthesises reporting from Blockonomi. It is not a copy of any one article — follow the source links above for the original reporting.
Original summary — not financial advice. This is an original TLT brief that summarises a development reported elsewhere and adds live market data for context; it is not the original article and reproduces no part of it. Follow the source link above for full details. Crypto is volatile and high-risk — always do your own research.