Publishing a public package with an internal package's name but a higher version is?
- Typosquatting a package
- Version pinning bypass
- Watering-hole attack
- Dependency confusion
Build tools that check public registries may prefer the higher version and pull the attacker's code.
Play Cybersecurity ▸