Safety failure
Realized harm
Claude Code deleted a decade of Bengaluru heritage-inscription records while clearing a cache; its own kill attempts were blocked by the safety layer
AIR-2026-0209 AIR record · 2026-07-claude-code-bengaluru-inscriptions-data-loss
A real party was affected. This incident caused actual consequences, not a demonstrated capability.
From the supporting source
On July 19, Claude Code (v2.1.204) wiped out four or five software programmes and some original photographs of Bengaluru’s inscriptions, hero stones, temples and coins, collected over the past decade.deccanherald.com
The record
Disclosed
2026-09-02
Occurred
2026-07-19
Vendor
Anthropic
Product
Claude Code (v2.1.204)
Risk domain
Agent behaviour › Unsafe actuation
System type
Generative model
Who acted
Agent acted — the agent itself executed the destructive shell command on the user's drive; no human ran or approved that command
Attack surface
Coding agent
Autonomy level
Semi-autonomous
Initial vector
Autonomous agent action no adversary
Impact type
Data destruction, Financial loss, Cultural heritage loss
Confidence
Medium
Submitted by
EAI Internal
Crosswalk
- OWASP Agentic Top 10 (2026)
- ASI01 – Agent Goal Hijack
- MITRE ATLAS
- AML.T0048 – External Harms
- NIST AI RMF
- MEASURE 2.6; MANAGE 1.3
- EU AI Act
- Annex III §1(c)
- ISO/IEC
- TR 24028; 24029-1; 23894
- AIUC-1
- C. Safety
- Scope
- agent misuse
- Mitigation
- Require confirmation for destructive actions; Implement dry-run modes; Use layered safety controls.
- Taxonomy
- Enkrypt AI agent risk taxonomy · Black-Box Red Teaming of Agentic AI: A Taxonomy-Driven Framework for Automated Risk Discovery
Blast radius
the local drive of the Bengaluru Inscriptions 3D Digital Conservation Project's honorary director: four or five software programmes and original photographs of inscriptions, hero stones, temples and coins collected over a decade, about 15% of the project's records; NAS backups survived; a fresh scan of 120 sites and Rs 15 lakh in new backup infrastructure
Capability abused
Defense & remediation
Recorded defense
Claude Code's safety layer and a sandboxed working environment; the safety layer blocked the agent's own attempts to kill the destructive process, twice
Guardrail kinds
Permission scope, Sandbox isolation
Guardrail outcome
Silent
Fix shipped
none reported; more than a month after the incident the user had received no response from Anthropic. The Mythic Society is spending Rs 15 lakh on a second NAS and offsite tape backups
Taxonomy & references
Curator notes
Reported by Deccan Herald (Barkha Kumari), Metrolife, 2 September 2026; the article quotes the affected user's earlier post on X but that post is not used as the source here. The agent was testing software it was developing and clearing a cache when, in the user's words, 'a quoting error in an AI-generated command turned the instruction into delete everything'. The agent recognised the error and tried to kill the process; the safety layer blocked the kill twice. The source does not establish that this layer governed the earlier destructive action, while the user separately reports that the command escaped the sandbox boundary, so the two controls do not support one aggregate held-or-defeated outcome. The user, heritage conservationist and former IT professional Udaya Kumar P L, shut the machine down after about four minutes. Data on the Mythic Society's NAS was safe; the local drive was lost. The user says the agent breached the sandboxed environment; the article does not detail the sandbox configuration. Notable for this corpus: the user states there is 'no register for such AI failures, no regulator to notify, no deadline for companies to respond'. Deccan Herald could not reach Anthropic for comment. Same failure shape as the Replit production-database deletion and the Gemini CLI file loss: a coding agent's destructive shell action on real data with no adversary, and no read-after-write verification.
Supporting sources
Cite as
Enkrypt AI. "Claude Code deleted a decade of Bengaluru heritage-inscription records while clearing a cache; its own kill attempts were blocked by the safety layer". AIR, AIR-2026-0209. https://agentincident.vercel.app/i/AIR-2026-0209/ (accessed 2026-10-19).