Web3Auth Security Incident: Investigation Findings and Recovery Update
We are sharing an update on the recent security incident affecting certain Web3Auth embedded wallets. This update sets out what happened, who was affected, what we have done and what users should do. Please see the recovery lookup for more information.
We recognise the seriousness of this incident and the impact on affected users, developers and partners. We apologise for any inconvenience caused.
What happened
On 6 November, we confirmed a security issue in Web3Auth infrastructure affecting certain embedded wallets, which resulted in unauthorised access to some accounts.
Our engineering teams began investigating the issue, assessing its potential impact and taking steps to contain the risk. As a precaution, we temporarily paused affected embedded wallet services while implementing additional security measures. We took these measures to protect the integrity of the services and to protect users.
In parallel, we worked with Keplr and our own security specialists to trace and recover affected user assets. Recovery efforts remain ongoing, including work to secure additional staked assets as they become available following unbonding periods.
The investigation remains ongoing.
Who was affected
The incident affected certain wallets created through social login using older Web3Auth infrastructure, primarily Keplr, as well as Torus Wallet and a small number of other applications.
Our investigation identified a number of potentially affected wallet addresses. We are continuing to work directly with affected applications to ensure users receive accurate information and appropriate guidance.
Our response and recovery efforts
Since identifying the incident, we:
- Disabled the affected services and removed the legacy functionality.
- Implemented additional authentication checks and security controls before restoring access for existing users on 12 November.
- Worked with Keplr and security specialists to secure user assets, with recovery efforts and verification ongoing.
- Worked with blockchain intelligence providers and exchanges to trace stolen assets and support recovery efforts.
- Increased monitoring and undertaken further security testing of the affected infrastructure.
Our immediate priority remains protecting affected users and returning recovered assets safely.
We are developing a process that will allow users to verify whether their wallets were affected and obtain information about the return of assets that were recovered. Further details will be published through our official channels once the process is ready.
Strengthening our security
We hardened the services and infrastructure supporting the legacy endpoint before resuming the service. New users can no longer onboard the legacy version of the service. We are also reviewing the security requirements for applications integrating Web3Auth and will provide developers with updated guidance on supported SDK versions and any changes required to maintain secure authentication. Further technical guidance will be shared directly with affected developers and partners as these requirements are finalised.
We recognise that restoring trust requires more than containing and resolving the immediate incident. It requires understanding the changing threat environment and consistently improving our security posture.
As part of restoring service, we ended support for older versions of our SDKs. These versions can no longer log in to the Web3Auth network. Applications using them need to upgrade to restore access for their users.
The versions no longer supported are:
- Web (React, Vue, JS): v9 and earlier
- React Native: v8 and earlier
- Android: v9 and earlier
- iOS: v11 and earlier
- Flutter: v6 and earlier
- Unity: v6 and earlier
- Single Factor Auth SDKs
Applications using the CustomAuth SDK or tKey SDK need to set useDKG=false in their configuration for new user logins to work, alongside updating to the latest version.
Single Factor Auth SDKs on legacy networks will not resume new user onboarding. Existing users can still log in. Upgrading to the latest Web3Auth SDKs will work as a replacement.
Logins and wallet access have resumed for existing users on all current SDKs and networks. Applications using our latest SDKs on Sapphire Mainnet can onboard existing and new users without any changes.
As a precaution, the following remain temporarily paused:
- New user logins on legacy networks (Legacy Mainnet, Aqua, Celeste, Cyan and MPC). Existing users can still log in.
- Facebook logins across all networks.
We are working on restoring signup functionality for users on legacy networks. We expect this by 23 November 2026. We will share an estimated timeline for restoring Facebook logins as soon as one is available.
We will also retire further legacy SDK versions, including v10, by December 20th 2026. Developers should use our migration guides to plan their upgrade. We will share further technical guidance directly with affected developers and partners.
What users should do
Affected users should only follow guidance published through official Web3Auth and Keplr channels.
Users can check whether their wallet has been identified as potentially affected and view the status of associated asset recovery efforts through our recovery lookup site, https://web3auth.io/keplr-recovery/.
Details on the return of recovered assets will follow through official channels.
Never share private keys, seed phrases or passwords, and be cautious of unsolicited messages claiming to offer recovery assistance.
We will continue to provide updates as the investigation and asset recovery process progress.
How users can protect themselves
- Follow only the recovery instructions on official Web3Auth and Keplr channels.
- Do not share a seed phrase, a private key, or a password with any person.
- Do not answer direct messages that offer help with asset recovery. Web3Auth does not send such messages.
- Compare each recovery address with the addresses on our official channels.
For support, please contact hellow3a@web3auth.io.
Protecting users and rebuilding trust remain our highest priorities.