Skip to main content
SAICA-KG

Incidents

Autonomous coding agent imports hallucinated "starlette-reverse-proxy" during build

An autonomous coding agent emitted `import starlette_reverse_proxy` during build — a package that didn't exist. Crash was benign; surfaces the pre-registration slopsquat attack surface.

2025-05-01security breachplausible

Description

Trend Micro's slopsquatting write-up documents a 2025 observation in which an advanced autonomous coding agent emitted code depending on a nonexistent Python package `starlette-reverse-proxy`. The build failed with `ModuleNotFoundError`, so the specific session was harmless. The significance is the mechanism: the agent produced plausible-sounding package names without a pre-generation existence check. If an attacker had pre-registered the name on PyPI (a low-effort operation), the next agent run with a similar prompt could have imported attacker-controlled code. The observation is one of several 2025 sightings that moved slopsquatting from theoretical to operational.

Exhibited failure modes

  • Fabrication — Generating reference to non-existent APIs, packages, or symbols.
  • Supply-chain attack — Slopsquatting, typosquatting, compromised MCP servers.

Affected systems

  • unnamed autonomous coding agent

Mitigated by

  • Socket — Dependency supply-chain scanner that inspects packages before install.

Documented by

Sources

Notes

Date is approximate (publication month); Trend Micro did not provide a precise event date. `reproducibility: plausible` (single-source) because the specific agent was not named.

View raw YAML on GitHub →