For Heads-of · Practitioner

Slopsquatting

Registering software package names that AI coding assistants tend to invent, so that a developer who installs a suggested but non-existent package installs the attacker's code instead.

  • package hallucination
  • software supply chain
  • AI coding
  • typosquatting

How it works

Language models generating code sometimes import packages that do not exist, and many of the invented names recur when the same prompt is repeated. A 2025 study of 16 code-generating models found that about a fifth of the packages they suggested did not exist, and that 43% of the invented names reappeared every time the same prompt was rerun. An attacker who registers a recurring name on a public package registry then waits for developers, or coding agents, to install it.

Why it matters

AI-assisted coding is now routine, and coding agents can install dependencies without a person reading the name. Slopsquatting turns a model's hallucination into a software supply-chain compromise inside the organisation's own build.

Controls

Install dependencies only from an approved internal registry or allow-list, hold new or rarely used packages for review, check every AI-suggested dependency before use, and do not let coding agents install packages unsupervised. The register entry is LLM application supply chain vulnerabilities.

Sources

Related Terms

Related risks and controls

← Back to Glossary