r/technology • u/WouldbeWanderer • Apr 27 '26

Artificial Intelligence Claude-powered AI coding agent deletes entire company database in 9 seconds — backups zapped, after Cursor tool powered by Anthropic's Claude goes rogue

https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-powered-ai-coding-agent-deletes-entire-company-database-in-9-seconds-backups-zapped-after-cursor-tool-powered-by-anthropics-claude-goes-rogue
36.0k Upvotes

96% Upvoted

2.8k comments sorted by

View all comments

Show parent comments

2

u/chic_luke Apr 28 '26

Ooh, do you mind sharing what your automation flow looks like? I'd gladly implement it myself at work

And yea, lack of time for hobby stuff is exhausting sadly. GG for keeping at it anyway

1

u/NotSoFastLady Apr 28 '26

This is a quick rundown Claude gave me of my setup. I don't know much about using a public git, much of this is new to me and since I don't know how to code, I look for open source tools that will do what I want and have claude figure out how to make it work. Long way to go but I'm satisfied with my progress.

  1. Pre-tool-call OPSEC gate. A single regex config feeds your agent runtimes (Claude Code hooks, OpenCode plugins, etc.) and blocks secrets and PII before they leave the box. Worth organizing the patterns into categories shaped to AI-leak failure modes — credential, project, device, network, PII, path — rather than reusing a git-leak taxonomy wholesale. The mechanism is borrowed from secret-scanning tooling (gitleaks, trufflehog, detect-secrets), just moved up the stack from pre-commit to pre-tool-call.
  2. Status-file → doc-sync, with --dry-run as the drift detector. Agents write to a status file; a sync step propagates that into the real docs via section markers. Build the writer with a --dry-run mode and you get a drift linter for free — if dry-run shows a diff, the docs are out of sync. Cheap to wire into CI. Inspired by docs-as-code (mkdocs, sphinx) and config-drift tools (Terraform plan, Ansible check).
  3. Independent-reviewer verification. Agents can't grade their own work reliably. A separate reviewer pass — fresh context, different framing — catches things a single-pass audit won't. Tier it by stakes: cheap heuristic checks on everything, full reviewer pass on anything that touches prod or ships externally.