Web3Auth Updates on Security Incident, Services to Resume Gradually

iconKuCoinFlash
Share
AI summary iconSummary
On November 14, Web3Auth shared an on-chain update regarding a security breach affecting embedded wallets created through Google or Apple login. The issue, first reported on November 7, permitted unauthorized access to certain accounts. Since November 8, the company has been recovering assets via white-hat operations and publishing multi-chain verification addresses. Login functionality is being gradually restored, but users must upgrade to SDK v10 or v11. New user registration is scheduled to resume on the Legacy network by November 23.

ME News reports that on November 14 (UTC+8), Web3Auth released an update regarding a security incident. On November 7, a security issue occurred in its infrastructure, affecting certain embedded wallets created via Google or Apple login—including wallets used by third-party applications such as Torus Wallet and Keplr—resulting in unauthorized access to some accounts. Starting November 8, Web3Auth initiated a white-hat asset recovery operation, transferring at-risk assets to secure recovery wallets and publishing multi-chain verified addresses. Existing user login functionality has been gradually restored, but users must upgrade to SDK v10 or v11. New user registration is expected to resume on the migrated Legacy network before November 23. (Source: Foresight News)

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.