liveBook · Manning

Slopsquatting

As explained in Vibe Engineering

An attack in which an attacker registers package names that language models are likely to hallucinate so developers may install malicious software.

Slopsquatting exploits package hallucinations: an attacker registers a package name that coding models commonly invents, then waits for a developer or automated pipeline to install malicious software. The risk grows when generated dependencies enter agent workflows with large blast radii and little review. section 5.2.4

Treat every AI-suggested dependency as untrusted input:

  • Verify that the package exists in the intended registry before running an install command. section 8.2.4
  • Question whether the dependency is necessary; generated code often adds libraries that a small implementation could avoid. section 8.2.4
  • Scan dependencies for vulnerabilities, compatible licenses, maintenance signals, suspicious ownership changes, and provenance. section 8.2.4
  • Do not treat lower hallucination rates or registry defenses as eliminating the attack class; generated dependency names remain a structural risk. section 5.2.4

The hallucinated huggingface-cli package

Models repeatedly recommended a Python package named huggingface-cli, although the real command-line installation uses pip install -U "huggingface_hub[cli]". After a researcher registered the nonexistent name on PyPI as an empty package, it received more than 30,000 genuine downloads in three months, demonstrating how plausible model output can create a ready-made supply-chain target. section 5.2.4

How Vibe Engineering covers it

How deep it goes
Explains the attack mechanism, gives observed rates and a concrete incident, then stops short of analyzing malicious payload implementation.
Examples
Uses the hallucinated huggingface-cli package, PyPI registration, and documented hallucination-rate studies as evidence.
What it assumes
Assumes familiarity with package installation and registries while teaching why generated dependency names require independent validation.
What you can do after
Operate dependency controls by verifying package existence, reviewing necessity, and running vulnerability, license, and supply-chain scans.
How it connects
Connects package hallucination with dependency scanning, software supply-chain security, malware, and AI-generated code.

Also explained in

Compare how 2 books explain slopsquatting →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.