Package typos and AI-generated names: what should teams change?

TL;DR: Typosquatting in npm and PyPI, plus slopsquatting from AI-generated package names, can turn a single mistaken install into code execution, credential theft, and downstream supply chain compromise, according to ThreatLocker. Package selection is now a governance decision, not just a developer convenience.

Editorial analysis by NHI Mgmt Group, based on content published by ThreatLocker: “How to mitigate typosquatting and slopsquatting attacks in npm and PyPI”.

Key questions

Q: How should security teams prevent malicious packages from running in build environments?

A: Start by treating package installation as an execution event, not a file download.

Q: Why do typosquatting and slopsquatting create code execution risk instead of just bad dependencies?

A: Because many package managers allow install-time scripts and other lifecycle hooks to run as part of setup.

Q: Where do package supply chain controls fail in practice?

A: They fail when teams rely on review alone and leave build runners over-privileged.

Practitioner guidance

• Verify dependency names before approval Check the exact package name against official documentation, repository metadata, publisher history, and expected release patterns before any install is allowed.
• Lock down package installation paths Use approved dependency lists, lockfiles, internal registries or proxies, and review every new package or version change before it reaches a build.
• Disable unnecessary install scripts Block lifecycle hooks such as npm install scripts in build contexts where they are not required, because those scripts are the execution point for many malicious packages.

Bottom line: Typosquatting and slopsquatting succeed because package selection often inherits trust without enough verification, which makes the install step a security decision.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →