If Your Agent Can Delete Production, It Eventually Will
The production database incident was not a model failure. It was a permission boundary failure. Prompts, plan mode, and confirmation buttons are not controls.
Incidents, failure modes, and the controls that survive when an AI agent has real credentials and real tools.
The production database incident was not a model failure. It was a permission boundary failure. Prompts, plan mode, and confirmation buttons are not controls.
A malicious npm release targeted developer credentials, GitHub Actions secrets, and AI tooling configs. That list is the threat model.
TeamPCP's third major supply chain hit in two weeks targeted foundational npm infrastructure, not an AI tool. Every JavaScript agent framework was in scope.
The source reveals that Claude Code's classifier behavior can be changed remotely via feature flags. Here's what that means for how you think about the controls underneath your AI agents.
The attack chain that compromised 4,000 developer machines, analyzed at the process and syscall level. What Rampart blocks, what it logs, and what it misses.
Two compromised versions of LiteLLM shipped a credential stealer that targeted exactly the locations AI agents use. That's not coincidence.
Traditional canary tokens detect human intruders. Snare is built for a world where the intruder is an AI agent with your credentials.
A taxonomy of how AI agents get compromised — from prompt injection to tool poisoning to supply chain attacks on agent workflows.
Claude Code runs as you. One malicious prompt is all it takes to wipe your files or exfiltrate your secrets. Here's why OS-layer interception is the only real defense.