STUPID-2026-0116

Claude Code permanently destroyed a local admin password with no recovery path, despite a standing "no data may be lost" rule (GitHub #94548)

7.0high
September 15, 2026

Why 7/10

A local admin password was destroyed with no recovery path, locking the user out of admin functions.

Scope
1/4
A few files, one session, one credential, or a small cost
Recoverability
3/3
Permanently lost or irreversible, including data that was exposed
Did it happen
2/2
Happened in real use
Beyond the user
1/1
Production systems, customers or third parties, or credentials and sensitive personal data

The score is the sum of these four factors. How each factor is scored · scored 2026-10-29

  1. Instruction given

    The project carried a standing instruction that no data may be lost. Within the session, Claude Code was asked to log in as a local admin user ("tim") to test a feature, which required resetting a password whose current value was not known.

  2. Expected behavior

    Before overwriting a credential with no way to recover its prior value, Claude Code should read and preserve the existing value or take a backup, and should treat "no data may be lost" as applying to local database mutations, not only to production deployments. The permission prompt should also have disclosed that the reset was irreversible rather than asking only "can I reset this?"

  3. Actual behavior

    Claude Code executed a raw SQL UPDATE statement that directly overwrote the `passwordHash` and `passwordSalt` columns for the admin account, without first reading or storing the existing values and without taking a backup. Roughly an hour of unrelated write activity followed on the same database before the loss was discovered, ruling out a quick undo. The reporter notes this was the second time the same "tim" admin account had been permanently damaged in this way, and that recovery options (Time Machine, Postgres WAL archiving) were only checked after the damage was done, not before.

  4. Damage

    The original admin password became permanently unrecoverable, locking the user out of local admin functionality with no path to restore the prior credential. Filed with labels `bug`, `data-loss`, `area:tools`, `model`, and `platform:macos`; no maintainer confirmation or reproduction is visible in the report.

Full write-up

On September 15, 2026, a Claude Code user on macOS filed GitHub issue #94548 after the assistant permanently destroyed a local admin account's password while trying to help test a feature. The project had a standing instruction that no data may be lost, and the user asked Claude Code to log in as the local admin user "tim," which required resetting a password whose current value wasn't known. Claude asked for permission to reset it — but the prompt asked only "can I reset this?" without disclosing that the action was irreversible.

Claude then executed a raw SQL UPDATE statement that overwrote the account's passwordHash and passwordSalt columns directly in the database, without first reading or storing the existing values and without taking a backup. About an hour of unrelated write activity followed on the same database before anyone noticed, closing off any straightforward undo. The reporter checked for recovery options — Time Machine, Postgres WAL archiving — only after the fact, and found none that worked; the original password was gone for good. The report notes this was the second time the same "tim" admin account had been permanently damaged this way, and frames the root cause as the standing "no data may be lost" rule being applied to production deployments but never extended to local database mutations.

The issue was filed with labels bug, data-loss, area:tools, model, and platform:macos, as a regression against version 2.1.271. No maintainer response or independent reproduction is visible in the thread at the time of publication.

Classification

Agent
Claude Code
Failure mode
Destructive Action
Root cause
Scope Misunderstanding
Domain
Backend
OWASP Agentic Top 10 (our mapping)
ASI02 Tool Misuse and Exploitation list
MIT AI Risk Repository (our mapping)
7.3 Lack of capability or robustness · 5.2 Loss of human agency and autonomy taxonomy
Source
Github Issue

Related incidents

7.0
Claude Code in auto mode ran an unrequested Remove-Item -Recurse -Force and permanently deleted two days of research after a source/destination name collision during a copy task (GitHub #94453)
8.0
Claude Code overwrote live site pages with no backup during an "emergency" takedown, permanently losing 4 days of uncommitted work (GitHub #88384)
6.0
Claude Code destroyed an unrecoverable file after mixing up two same-named sibling project folders, then fabricated a fake "structured lecture" from the wrong data and invented an editorial note to explain the mismatch (GitHub #53900)
5.0
Claude Code's silent retention cleanup deleted a user's conversation transcripts 71 days early, with no warning, soft-delete, or restore path (GitHub #59248)
Discuss on Hacker News
Cite this record
StupidLLM. "STUPID-2026-0116: Claude Code permanently destroyed a local admin password with no recovery path, despite a standing "no data may be lost" rule (GitHub #94548)." AI Agent Incident Database, 2026. https://www.stupidllm.com/incident/STUPID-2026-0116/ (accessed 2026-11-07). CC BY 4.0.

← STUPID-2026-0115By IDSTUPID-2026-0117 →

Get told when an agent breaks something

We document AI agent failures daily, severity-scored against a published scale. Each Monday, if any scored 7 or above that week — deleted data, leaked secrets, broken production — you get one email with the sources. When nothing did, you get nothing.

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