Roundup

Every agent incident we’ve taken apart, in order

A running timeline of real incidents with AI agents, MCP servers and AI tools, from deleted databases to poisoned packages, each linked to its full breakdown.

By the NoFly team

In this post2 min read
  1. 01How to read this
  2. 02The timeline
  3. 03How NoFly helps
NoFly helps withProtectDiscoverAttack

How to read this

Every entry below is a real, publicly reported incident. Each breakdown links the original reporting, walks through what the agent did, and names the control that would have stopped it.

Most of them needed no exotic attacker. Agents acted with the access they had been given, on instructions nobody checked, and the damage was done before anyone read a log.

The timeline

  1. AttackPHP (CVE-2026-109618, CVE-2026-109619)PHP2Shell, and where an AI firewall can and cannot stand in its wayWith NoFly: A PHP service reachable only through the MCP gateway receives re-serialized JSON-RPC, not the attacker’s raw request, which narrows how these flaws can be reached. It does not replace the patch.
  2. AttackCursor, Codex, Gemini CLI and AntigravitySeven ways out of a coding agent’s sandbox, without breaking the sandboxWith NoFly: A command that reaches the container daemon, or writes a file a trusted component runs, is decided before it runs, not left to the sandbox to contain.
  3. MistakeCodex with GPT-5.6 SolCodex deleted users’ home directories in Full Access modeWith NoFly: A recursive delete of a home directory is held for a person before it runs.
  4. AttackGitHub Agentic WorkflowsA public issue could make a GitHub agent post a private repo in the openWith NoFly: An agentic workflow that an outsider can trigger, reads another repository and can post the result is read as one shape and flagged before it runs.
  5. Supply chainClaude Code, Gemini CLI and Cursor config filesA worm hid credential stealers in AI agent config files in Microsoft repositoriesWith NoFly: Agent settings, hooks and rules files are read like code, and a hook that runs a script from the repository is flagged.
  6. AttackCodex CLI on WindowsA web search that ended in code running on the hostWith NoFly: A write that drops a developer-tool executable into the working directory is held, because that is where Windows looks before the system path.
  7. MistakeCursor with Claude Opus 4.6A Cursor agent deleted a production volume and its backups in nine secondsWith NoFly: The delete is held for a person, with its real target and the token it uses.
  8. ExposureContext.ai and VercelAn AI app’s OAuth grant became a way into VercelWith NoFly: AI apps holding grants to work accounts are listed with their scopes, and can be revoked before a vendor’s breach becomes yours.
  9. Supply chainLiteLLM (PyPI)Two LiteLLM releases on PyPI carried a credential stealerWith NoFly: Packages on every machine and service are matched against advisories, so the places that pulled the bad versions are a list.
  10. MistakeClaude Code with TerraformClaude Code ran terraform destroy and took down a production platformWith NoFly: A destroy against production is held for a person, with the exact command and its target in front of them.
  11. Supply chainOpenClaw and ClawHub341 malicious skills on ClawHub pushed infostealers to OpenClaw usersWith NoFly: Skills are read like code before they run, and a setup step that pipes a remote script into a shell is flagged.
  12. AttackServiceNow Now AssistOne ServiceNow agent could recruit another to do what it could notWith NoFly: Agents built in vendor consoles are inventoried with their reach, and hand-offs that widen authority are caught.
  13. Supply chainpostmark-mcp (npm)A fake Postmark MCP server copied every email it sent to an attackerWith NoFly: A new version of an approved server is a change to review, and a server caught reaching out in the sandbox is quarantined.
  14. Supply chainNx build system (npm)Malicious Nx packages turned developers’ AI CLIs into secret huntersWith NoFly: The inventory lists the machines that installed the bad versions and the keys to rotate, and flags AI CLIs set up to skip their checks.
  15. ExposureSalesloft DriftStolen tokens from an AI chat integration opened hundreds of Salesforce orgsWith NoFly: Every AI app holding a grant into your systems is listed with what it can reach, and can be revoked in one place.
  16. AttackGemini CLIA README could make Gemini CLI run hidden commands without askingWith NoFly: The gate reads the whole command, including everything after the semicolon, and names where the instruction came from.
  17. MistakeGemini CLI on WindowsGemini CLI lost a user’s files after assuming a folder existedWith NoFly: A rule can hold bulk file moves for a person, and every step is kept in one record, so a loss can be traced command by command.
  18. MistakeReplit AgentReplit’s agent deleted a production database during a code freezeWith NoFly: Destructive writes to production wait for a person, who sees the statement itself.
  19. Supply chainAmazon Q Developer for VS CodeAmazon Q’s VS Code extension shipped with a prompt to wipe machines and cloud accountsWith NoFly: The same instruction in an agent NoFly hooks meets a hold, and the inventory shows which laptops ran the bad version.
  20. Attackmcp-remote (npm)Connecting to a malicious MCP server could run commands on your laptopWith NoFly: Vulnerable packages are found across laptops, and agents can reach remote servers through one gateway instead.
  21. AttackSupabase MCP server in CursorA support ticket could make an agent paste secrets back to a customerWith NoFly: Tool results are screened before the agent reads them, and MCP configs holding live keys are flagged.
  22. AttackMicrosoft 365 CopilotOne email could turn Microsoft 365 Copilot into a data leakWith NoFly: Content from outside is screened before an agent acts on it, and data is followed from where it was read to where it is sent.
  23. AttackGitHub MCP serverA public GitHub issue could steer an agent into leaking private repositoriesWith NoFly: Tool results are screened before the agent reads them, and each agent reaches only the repositories its task needs.

How NoFly helps

  • Protect

    Every command and tool call is decided before it runs, so a mistake or a hijacked instruction meets a gate instead of a production system.

  • Discover

    When a new incident or advisory lands, NoFly checks which of your machines run the affected tool or package, and what they already did.

  • Attack

    Attack simulation fires the same families of technique, such as hidden instructions in content and poisoned tools, at your own agents on a schedule.

Keep reading

More from the blog.

Find out what your AI is allowed to do today.

Book a call and we will map your agents, MCP servers and keys with you, or start on one laptop with the free scan.

Book a demo
npm i -g @nofly/agent