Article Details

Scrape Timestamp (UTC): 2025-10-27 13:14:47.520

Source: https://www.theregister.com/2025/10/27/x_passkey_reset/

Original Article Text

Click to Toggle View

X says passkey reset isn't about a security issue – it's to finally kill off twitter.com. Social media site dispatches crucial clarification days after curious announcement. X (formerly Twitter) sparked security concerns over the weekend when it announced users must re-enroll their security keys by November 10 or face account lockouts — without initially explaining why. The cryptic mandate from X Safety on Friday led many to suspect a security breach was behind it. When a platform forcibly rotate security keys, it's often a sign it is working through incident response protocols – eradicating adversaries from a network and keeping them out. But on Sunday, Elon Musk's social media mouthpiece finally gave the all-important explanation: it pertained the twitter.com domain that's still in use and redirects to x.com. "To clarify: this change is not related to any security concern, and only impacts Yubikeys and passkeys – not other 2FA methods (such as authenticator apps)," X Safety stated. "Security keys enrolled as a 2FA method are currently tied to the twitter.com domain. Re-enrolling your security key will associate them with x.com, allowing us to retire the Twitter domain." Physical security key currently tied to the twitter.com domain won't work when users attempt to authenticate from the x.com domain, so they must be re-enrolled in preparation for what sounds like a sunsetting of the Twitter domain. Christopher Stanley, security engineer at X and SpaceX, said he asked the Safety team to issue the clarification after seeing the puzzled reactions from some in the security community. "Getting off of Twitter enrolled keys so we can stop doing hacky things for domain trust," he responded to one user. "Physical security keys are cryptographically registered to Twitter's domain and need to be re-enrolled under X." Passkey push The required re-enrollment of passkeys not only potentially signals the end of the Twitter domain, but also the company's commitment to the passkey revolution, which many others have joined. All the big tech companies are edging toward the passwordless future. Microsoft has long told customers they won't have the option to forgo the passwordless push, while Google keeps adding features to increase users' trust in the new way of authenticating. Passwords can be, and all too often are, stolen through various means. The method of authenticating is susceptible to attacks such as phishing and social engineering. As Reg readers know, in a passkey world passwords are replaced by physical devices - smartphones and laptops - used to access the online services that require authentication. Passkeys make these account attacks much more difficult to pull off, and in many cases nullify them. While phishing attacks may drop significantly, cybercriminals always find alternative ways to break into organizations. Passkeys don't solve the software vulnerabilities problem – separate, slow-going work continues on that front – and attempts to recruit insiders to carry out attacks like ransomware will likely increase.

Daily Brief Summary

MISCELLANEOUS // X Requires Passkey Re-enrollment Amid Domain Transition to x.com

X, formerly Twitter, announced a mandatory re-enrollment of security keys by November 10, initially causing security breach speculation.

The re-enrollment is necessary due to the transition from the twitter.com domain to x.com, not due to any security incident.

Only Yubikeys and passkeys are affected, while other 2FA methods like authenticator apps remain unchanged.

Physical security keys are currently linked to the twitter.com domain and must be re-registered to function with x.com.

This move aligns with X's broader strategy to phase out the Twitter domain and embrace passwordless authentication.

The shift to passkeys is part of a larger industry trend towards enhanced security and reduced reliance on traditional passwords.

While passkeys enhance security against phishing, they do not address software vulnerabilities or insider threats.

The change reflects ongoing efforts by major tech companies to promote more secure, passwordless authentication methods.