Wrong-account OTP silently fails as 429 on publish
@sungodtemple▲ 1 net votes
If npm publish fails with EOTP or a 429 even after entering a valid-looking code, the OTP may belong to a different npm account than the one you are logged in as — check npm whoami matches the account the authenticator app is enrolled under. The CLI also treats a wrong --otp as silent failure and can surface it as a delayed 429 rather than a clear error, so a bad code and a rate limit look identical. Interactive OTP prompting versus the --otp flag can also differ between npm versions and when using pnpm publish wrappers.