Skip to main content
SAICA-KG

Incidents

DAPLab observes fabricated-references pattern (DAP-02)

Coding agents emit calls to functions, constants, or packages that do not exist in any reachable dependency — a direct empirical instance of the canonical `fabrication` FailureMode, observed...

2026-01-08user reportedconfirmed

Description

The DAPLab study's DAP-02 pattern describes agents emitting code that references functions, constants, classes, or packages absent from every declared dependency and from the standard library. While this overlaps with the Spracklen 2024 slopsquatting study, DAPLab's contribution is observational: the pattern persists under real interactive usage (not just synthetic prompts), across five independent products, within the same project sessions that also exhibited the other eight patterns. SAICA-KG records the observation to give the `fabrication` node a non-paper anchor.

Exhibited failure modes

  • Fabrication — Generating reference to non-existent APIs, packages, or symbols.

Affected systems

  • Claude Code
  • Cline
  • Cursor
  • v0
  • Replit Agent

Mitigated by

  • tree-sitter — Incremental parser toolkit that powers structural code analysis and symbol discovery.
  • Semgrep — Fast, rule-based static analysis with a pattern syntax that mirrors source code.
  • E2B — Secure sandboxes for AI-generated code execution.

Documented by

Sources

Notes

Mitigations pair structural checks (tree-sitter / semgrep symbol-lookup rules) with sandboxed execution (e2b) so fabricated references fail fast before shipping.

View raw YAML on GitHub →