e5ad02b2-9
Keplr, Torus Social-Login Wallets Affected by Web3Auth Flaw
Web3Auth said an infrastructure flaw affected some Keplr, Torus Wallet and other social-login wallets. Access returned Nov. 12, while recovery work continues.

Outputs
Web3Auth's Nov. 18 update identified some social-login wallets used through Keplr, Torus Wallet and other apps as affected.
Existing users regained login and wallet access on Nov. 12.
Facebook sign-ins remain paused across all networks.
New registrations remain suspended on the Legacy network.
Some funds must be unstaked before transfer during recovery.
By Tom Whitfield
Existing users regained login and wallet access on Nov. 12, but Web3Auth's Nov. 18 investigation update said an infrastructure security flaw had affected some social-login wallets used through Keplr, Torus Wallet and a small number of other apps.
The finding does not mean every wallet in Keplr or Torus Wallet was affected. Web3Auth said it had “identified some embedded wallets created through social login” and had closed the affected legacy services. The company also strengthened its authentication measures.
The Nov. 18 update followed the Nov. 12 restoration by six days. It did not disclose a dollar loss, a user count or a complete list of affected applications, so the disclosed scope remains limited to some embedded wallets across the named services.
The absence of a loss figure means the update does not support a claim about the scale of asset exposure. Its stated operational focus is narrower: restoring existing access, containing legacy infrastructure and moving identified assets through a controlled recovery process.
What access restrictions remain?\n
Three operating limits define the current service state:
- Facebook sign-ins remain paused across all networks, removing the Facebook authentication route while the incident and recovery process continue.
- New registrations remain suspended on the Legacy network, preventing additional accounts from entering that environment.
- Some older SDK versions are no longer supported, narrowing compatibility for applications still integrated with those releases.
The distinction matters because the Facebook pause applies across networks, while the registration suspension applies to the Legacy network. Restoring existing access therefore did not reopen Facebook authentication or restore new Legacy registrations.
How are affected assets being recovered?\n
Web3Auth is working with Keplr and blockchain analytics firms to recover affected assets. Some funds must be unstaked before they can be transferred, requiring a position to be unwound before the recovery movement can proceed.
Web3Auth and Keplr have also been moving affected assets into recovery wallets and publishing verified destination addresses in earlier asset-transfer updates. Those published addresses provide the reference point for verifying where recovery assets are being sent.
Users can determine whether a wallet was affected and follow recovery progress through earlier coverage of Web3Auth's wallet-impact and recovery-status page. The workflow separates impact checks from recovery monitoring: a user first needs to establish whether the wallet falls within the affected set, then track the status of the associated assets.
What does the flaw change operationally?\n
Closing the affected legacy services and strengthening authentication are the stated containment measures. Ending support for some older SDK versions removes those releases from the supported operating environment, while the registration and Facebook-sign-in suspensions limit new access paths.
The incident also separates service restoration from asset recoverability. Existing users regained login and wallet access on Nov. 12, but affected assets still require movement to recovery wallets, and some funds must clear a staking position before transfer.
Keplr and Torus Wallet enter the finding because some social-login wallets created through their apps fell within the affected group; the update does not identify every wallet in either product as affected. Web3Auth and Keplr's use of recovery wallets, together with published destination addresses, adds a verification step between asset identification and transfer.
The next checkpoint is asset mobility, not basic sign-in. Facebook sign-ins and Legacy registrations remain suspended, and Web3Auth's Nov. 18 update provided no deadline for lifting those limits or completing asset recovery.
via tokenpost.com (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
1,440 articles