I've Just Liberated My Modules
The fact that this is possible with NPM seems really dangerous. The author unpublished (erm, "liberated") over 250 NPM modules, making those global names (e.g. "map", "alert", "iframe", "subscription", etc) available for anyone to register and replace with any code they wish.<p>Since these libs are now baked into various package.json configuration files (some with 10s of thousands of installs per month, "left-pad" with 2.5M/month), meaning a malicious actor could publish a new patch version bump (for every major and minor version combination) of these libs and ship whatever they want to future npm builds. Because most package.json configs use the "^1.0.1" caret convention (and npm --save defaults to this mode), the vast majority of future installs could grab the malicious version.<p>@seldo Is there a plan to address this? If I'm understanding this right, it seems pretty scary :|<p>[1] <a href="https://medium.com/@azerbike/i-ve-just-liberated-my-modules-9045c06be67c#.6je6fouj8" rel="nofollow">https://medium.com/@azerbike/i-ve-just-liberated-my-modules-...</a>