npm's 2FA being broken for digital passkeys and linux machines #212158
Unanswered
Saturn-sepehr
asked this question in
npm
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
Body
Hello everyone :3
I am just posting this to bring attention to an issue I have been experiencing for 9 days.
Issue is, I am trying to remove two tags from my npm package, gclass-anims.
I have tried doing it using a Granular Access Token with Bypass 2FA enabled.
It didn't work, as seen in the terminal log below :
file.txt
I send a ticket to npm support via their official ticketing system on October 27 2026, but got no reply.

Later, I tried setting up 2FA to see if I can resolve the issue myself.

(Unfortunately due to sanctions and import restrictions in my region, YubiKeys cost 150 USD)
Things i have tried :
Using KeePassXC on both Firefox and Chromium on Linux mint 22.3
which resulted in the following error :
Error! Passkeys request cancelled
I have tried using my own phone as a physical key
which resulted in :
the website asking me for an OTP which NEVER arrived due to my phone being the passkey
but also not prompting for a QR code scan or a code or anything!
Luckily i managed to remove 2FA because i was still logged into my account on my desktop browser.
When i tried to use the account recovery option it redirected me to https://www.npmjs.com/recovery-support/message/email which gave me a 404 page.

Note : using OIDC/Trusted Publishing is also a dead-end due to the fact that it also requires 2FA to be setup on the account
I have tried reaching out to npm's ticket system again regarding this issue with 2FA not working properly without physical keys but no response since October 31 2026

I am simply asking that npm fixes their 2FA system for digital passkeys
Cheers!
Maintainer of gclass-anims
Saturn_sepehr
All reactions