Dependency Confusion: Your Internal Package Name Is a Public Attack Surface
Publish a package with the same name as a company's private one, give it a higher version number, and package managers will happily install the attacker's code instead. Here's how it still works in 2026.