Keplr Halts Social Logins After Google and Apple Account Compromise
Keplr and Web3Auth contained a wallet incident affecting Google and Apple sign-in users while recovery efforts began and affected users were asked to stop depositing.
Keplr and Web3Auth contained a wallet incident affecting Google and Apple sign-in users while recovery efforts began and affected users were asked to stop depositing. This is an original Token Times brief synthesising 2 outlets (Blockonomi, BeInCrypto), plus live market data, as of Sun, 08 Nov 2026 17:00:02 UTC.
The incident exposed how social-login credentials can intersect with embedded-wallet access, making the security of restored accounts and funds held at flagged addresses important to affected users.
- Google and Apple sign-in accounts were affected
- Social logins were frozen and embedded wallets paused
- Recovery-phrase and hardware-wallet accounts were outside the reported scope
- An initial estimate placed about $6.01 million across eight destinations
Blockonomi and BeInCrypto both report that the Keplr wallet incident affected users who authenticated with Google or Apple, and that Web3Auth identified flagged addresses associated with funds secured for some users. Blockonomi adds that Keplr froze social login, Web3Auth paused its embedded-wallet service, and affected users were told not to deposit more assets; it also cites an initial Bitquery estimate of about $6.01 million spread across eight destinations. BeInCrypto places greater emphasis on the presence of user funds at flagged addresses, while Blockonomi focuses more heavily on containment and account scope; neither outlet contradicts the other on the core incident.
- Keplr Disables Social Logins After Reported Wallet Drains
- Keplr Halts Social Logins After Google and Apple Account Compromise — this brief
Keplr and Web3Auth are responding to a wallet-security incident that affected users accessing their accounts through Google or Apple sign-in options. Blockonomi reports that recovery efforts have begun, while the social-login system was frozen and Web3Auth paused its embedded-wallet service to contain the problem.
Affected users were instructed not to deposit additional assets into their accounts while the response continued. According to BeInCrypto, some addresses flagged during the incident hold funds that Web3Auth secured for users, linking the account compromise to assets stored under the platform’s custodial arrangements.
The two outlets agree on the affected login methods and Web3Auth’s role in protecting or securing user assets. Blockonomi provides additional operational detail and cites Bitquery’s initial tracking of roughly $6.01 million across eight destinations. BeInCrypto does not provide a competing loss estimate, instead emphasizing that some flagged addresses still contain funds secured for affected users.
The reported scope was narrower than all Keplr users. Blockonomi says recovery-phrase accounts and hardware-wallet accounts remained outside the incident, while Google and Apple sign-in accounts were affected. The distinction leaves recovery focused on the compromised social-login pathway rather than every type of wallet supported by the service.
The broader crypto market was comparatively subdued at the time of the report: total market capitalization stood at $2.61 trillion, the overall market was flat, and 
Bitcoin was up 0.39% over 24 hours. The Fear & Greed index registered 28, indicating a “Fear” reading. No specific coin from the market-data list was linked to the incident, leaving further account-restoration updates, the handling of flagged addresses, and the final scope of affected funds as the main developments to monitor.
Keplr Halts Social Logins After Google and Apple Account Com — questions & answers
Which Keplr accounts were affected?
Users who signed in with Google or Apple were affected. Recovery-phrase and hardware-wallet accounts were reported as outside the incident’s scope.
What did Web3Auth do after the hack?
Web3Auth paused its embedded-wallet service. It also reported that some flagged addresses held funds it had secured for affected users.
How much money was initially tracked?
Blockonomi cited Bitquery’s initial estimate of about $6.01 million across eight destinations. The figure was described as preliminary.
Which outlets reported this story?
This is an original Token Times brief that synthesises reporting from Blockonomi, BeInCrypto, with the key figures cross-checked for agreement across them. 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 Token Times 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.