Key questions/where-are-deployed-agents-exploited

Where are deployed AI agents actually being exploited?

moderate confidenceRevised Nov 17, 2026Reviewed assistant-drafted
Current answer

Exploitation often reaches deployed agents through connectors, credentials, tools and packages.

Disclosures show untrusted content entering agents through connectors and documents, and broad credentials expanding the effects of injected instructions. Some framework vulnerabilities reach code execution, and malicious agent packages and MCP servers have been used against real users. SQL Copilot’s reported actions inherit the connected user’s database privileges.

Salt’s October Manus demonstration adds an email-reading workflow in which untrusted code ran before an approval warning and reached the user’s sandbox and connected-account tokens; Salt states the flaw has been resolved. Embrace The Red reports that Copilot in Visual Studio and SQL Server Management Studio could be driven, including through indirect prompt injection, to rewrite its own protected configuration and run commands, fixed on 2026-10-13 per the researcher. Forever Security reported on 2026-10-29 that the browsers embedded in five desktop coding assistants (Cursor, GitHub Copilot, Claude Desktop, Codex and VS Code) form further trust boundaries, with impacts ranging from address spoofing and local-file access to host code execution in Cursor; by its account Cursor and Copilot were fixed and Codex and VS Code unresolved at publication. All three are researcher-controlled demonstrations that depend on specific products and settings, not evidence of attack campaigns or of automatic access to all of a user’s accounts.

The supply chain around agents is also a target. On 2026-10-21 a compromised release of the LiteLLM AI gateway on PyPI and Docker registries was built to steal cloud, developer and AI coding tool credentials; LiteLLM’s completed investigation, published on 2026-10-23, traces access to an unrevoked Agent Platform master key exposed in a public repository, followed by theft of GitHub credentials used against its release pipeline. This supersedes its initial response-log hypothesis. Cursor’s November 13 investigation traced tampered Claude Code builds in its marketplace cache to a credential exposed at Fireworks and unredacted credentials in historical training traces. Cursor says at most 5,000 users requesting affected versions on October 29 potentially received a tampered build. Microsoft Threat Intelligence’s code analysis describes host reporting and attempted persistent remote access. It does not establish execution on individual hosts, and its analysis found that the callback was designed to send names of key-like environment variables without their values. JFrog reported on 2026-10-26 that 42 hijacked GitHub repositories linked to an npm campaign carried execution hooks for Claude, Gemini, Cursor and VS Code, though the count does not establish how many developer machines ran them.

The findings behind it

7 corroborated

Each finding carries a status that changes as new work arrives. What the statuses mean.

Answer history

Answers are never edited after the fact. A revision adds a new answer and keeps the earlier ones here.

  1. 2026-11-17moderate confidencecurrentExploitation often reaches deployed agents through connectors, credentials, tools and packages.Correction: the Cursor figure is a ceiling on potential recipients, and Microsoft analyzed code behavior rather than verifying execution on individual hosts. The revision also incorporates Cursor’s November 13 account of the credential exposure.
  2. 2026-11-01moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.Adds Cursor’s marketplace compromise with Microsoft’s analysis of the injected code, JFrog’s hijacked repositories carrying agent execution hooks and Forever Security’s embedded-browser disclosures; direction and confidence are unchanged.
  3. 2026-10-24moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.Replaces LiteLLM’s preliminary response-log explanation with its completed investigation of the compromised release, cited by the finding on malicious or compromised agent packages.
  4. 2026-10-22moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.Adds the LiteLLM compromise, in which an AI gateway release stole the credentials agents and their operators rely on.
  5. 2026-10-19moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.Adds a researcher-reported case in which a coding agent could rewrite its own configuration to reach code execution.
  6. 2026-10-13moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.Correction: the earlier explanation called the Manus demonstration patched, but Salt’s source reports resolution without establishing a patch mechanism. The answer attributes that resolution to Salt; its direction and confidence are unchanged.
  7. 2026-10-13moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.Added the patched Manus email demonstration to the broad-credentials and approval-gate findings; distinguished warning timing, configured credentials and research evidence from observed attacks.
  8. 2026-10-01moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.Added the September 2026 disclosure about Copilot in SQL Server Management Studio, recorded as evidence for the finding on broad credentials (record embrace-the-red-sql-copilot-ssms-cve-2026-65669-2026). It fits the existing answer, so its direction and confidence are unchanged.
  9. 2026-09-25moderate confidenceMostly around the model: connectors, credentials, tools, and packages, rather than the model alone.First answer, drawn from the findings linked here.