STUPID-2026-0136

Claude Code's rm -rf followed a pnpm NTFS junction out of a Next.js template and wiped a developer's entire C:\Users profile — 165GB, 1.6M files (GitHub #36339)

9.5critical
March 19, 2026VerifiedReproducible
  1. Instruction given

    Using Claude Code v2.1.51 in Git Bash on Windows 11 with --dangerously-skip-permissions, scaffold a Next.js + Payload CMS project via `pnpm dlx degit` and resolve an incompatible workspace dependency.

  2. Expected behavior

    Delete only the newly scaffolded template folder; detect that pnpm had populated it with NTFS junctions rather than real directories before running any recursive delete, and never let a cleanup command escape the project folder into the user's home directory.

  3. Actual behavior

    After finding `workspace:*` dependencies incompatible with a standalone install, Claude Code ran `rm -rf /c/Users/guido/aldaba-v2` in Git Bash. pnpm had wired the template's node_modules with NTFS junction points; Git Bash's rm followed them as real directories instead of removing the links, and the delete escaped the project folder into the surrounding C:\Users\guido profile. No confirmation, warning, or error was shown before or during the deletion.

  4. Damage

    The reporter says the entire C:\Users\guido profile was destroyed — roughly 165.66GB across 1,593,350 files and 276,382 folders, including personal files, AppData, and active business data for a company. The user only noticed when the Desktop was empty. At the time of filing, recovery via a paid NTFS recovery tool was still in progress and no data had been recovered. The issue was filed with `data-loss` and `has repro` labels and ultimately closed as not planned, with no fix shipped; it cites two prior, similar junction-traversal deletion reports (#29249, #29023) as related issues.

On March 19, 2026, a developer using Claude Code v2.1.51 in Git Bash on Windows 11 filed GitHub issue #36339 after the agent destroyed their entire `C:\Users\guido` profile while cleaning up a scaffolded project. The agent had run `pnpm dlx degit payloadcms/payload/templates/website aldaba-v2` to create a Next.js and Payload CMS starter, then found the template's `workspace:*` dependencies incompatible with a standalone install and ran `rm -rf /c/Users/guido/aldaba-v2` to remove it. pnpm had populated the template's `node_modules` with NTFS junction points rather than ordinary directories or symlinks. Git Bash's `rm -rf` follows NTFS junctions into their real targets instead of deleting the link itself — the same gap already fixed in PowerShell Core 6+ but never backported to the Windows tooling Claude Code's Bash tool shells out to. The recursive delete escaped the project folder entirely and tore through the user's home directory: the reporter estimates 165.66GB across 1,593,350 files and 276,382 folders were destroyed, including personal files, AppData, and data for an active business. No warning or confirmation preceded the deletion; the user discovered it only after noticing the Desktop was empty. The issue was filed with `bug`, `data-loss`, and `has repro` labels and cites two earlier, similar junction-traversal deletions (#29249, #29023) as related reports — the same failure class recurring across different Windows package managers and projects. A GitHub Actions bot closed it as stale and "not planned" roughly six weeks later with no maintainer response and no fix shipped for this specific report.

Classification

Failure mode
Destructive Action
Domain
Infra

Related incidents

Get told when an agent breaks something

We document AI agent failures daily, severity-scored against a published scale. When one lands at 7.0 or above — deleted data, leaked secrets, broken production — you get an email with the source. When nothing does, you get nothing.

This database is callable over MCP — query it from inside your agent.