But they can't be stealing any identifying information right? At best it can count the number of times the package was downloaded.
Isn't the solution for npm to have tighter controls on where it will download packages from?
Isn't the solution for npm to have tighter controls on where it will download packages from?
This is why you should always shrinkwrap and run a private npm repository in production. Anything less is opening you up to remote takeover at the whim of a single package publisher.