3 ms·
I don't understand. The link could've come from anywhere (for example from a HN comment). How does just clicking on it give your package credentials to someone
by osa1 1y ago
I don't understand. The link could've come from anywhere (for example from a HN comment). How does just clicking on it give your package credentials to someone else? Is NPM also at fault here? I'd naively think that this shouldn't be possible.
For example, GitHub asks for 2FA when I change certain repo settings (or when deleting a repo etc.) even when I'm logged in. Maybe NPM needs to do the same?
- koil 1y agoAs OC mentioned elsewhere, it was a targeted TOTP proxy attack.
- hughw 1y agoSo, he clicked the link and then entered his correct TOTP? how would manually typing the url instead of clicking the link have mitigated this?
- Mogzol 1y agoThey wouldn't have manually typed the exact URL from the email, they would have just typed in npmjs.com which would ensure they ended up on the real NPM site. Or even if they did type out the exact URL from the email, it would have made them much more likely to notice that it was not the real NPM URL.
- dboreham 1y agoOP entered their credentials and TOTP code, which the attacker proxied to the real npmjs.com FWIW npmjs does support FIDO2 including hard tokens like Yubikey. They do not force re-auth when issuing an access token with publish rights, which is probably how the attackers compromised the packages. iirc GitHub does force re-auth when you request an access token.
- osa1 1y ago> They do not force re-auth when issuing an access token with publish rights, which is probably how the attackers compromised the packages I'm surprised by this. Yeah, GitHub definitely forces you to re-auth when accessing certain settings.
- deleted 1y ago[deleted]