prompt injection
A security risk in agentic systems where malicious instructions can manipulate model behavior through retrieved or connected content. The newsletter references it as a design and safety concern for agents.
Key Highlights
- Prompt injection is a core security risk in agentic systems because untrusted external content can override intended model behavior.
- Newsletter coverage shows that model defenses alone are not enough; containment and blast-radius reduction are recurring themes.
- Real-world examples connect prompt injection to credential theft, data exfiltration, and software supply chain compromise.
- For AI PMs, connectors, retrieval, permissions, and tool access are product decisions that directly shape prompt-injection risk.
- Recent discussion also highlights role confusion and destyling as important concepts in understanding and mitigating attacks.
Prompt Injection
Overview
Prompt injection is a security failure mode in AI systems—especially agentic systems—where untrusted content includes instructions that influence a model’s behavior in unintended ways. Instead of only following the user’s intent and trusted system rules, the model can be manipulated by text retrieved from documents, websites, emails, issue trackers, shared drives, or other connected sources. In practice, this often appears as indirect prompt injection, where the attack is embedded in external content rather than typed directly by the end user.For AI Product Managers, prompt injection matters because it turns ordinary product features—search, retrieval, browsing, email, code agents, file access, and connectors—into potential attack surfaces. The risk is not just bad answers; it can lead to credential theft, data exfiltration, unauthorized tool use, or harmful automated actions. The newsletter increasingly frames prompt injection as a core design and safety concern for agents, especially as teams move from chat interfaces to systems that can read, decide, and act across enterprise environments.
Key Developments
- 2026-03-07: Simon Willison highlighted Clinejection, based on reporting by Adnan Khan, describing an attack chain in which prompt injection in a GitHub issue title compromised an AI triage workflow and contributed to malicious NPM release publication.
- 2026-03-12: OpenAI published guidance on designing AI agents to resist prompt injection, emphasizing architectural and behavioral mitigations for agent robustness.
- 2026-05-26: Reporting on Microsoft Copilot Cowork described how agent-sent emails, external image rendering, and pre-authenticated OneDrive links created a path for prompt-injection-driven data exfiltration.
- 2026-06-01: Anthropic argued that model defenses alone are insufficient, sharing that Claude Opus 4.7 showed about 0.1% attack success on single prompt-injection attempts and roughly 5–6% after 100 adaptive attempts; it cited Mythos Preview as too risky to ship because of blast-radius concerns.
- 2026-06-19: Anthropic expanded on its containment approach across products, combining environment controls, model-layer controls, and limits on external-content/tool access; telemetry also showed how often users approve prompts and how Claude Code auto mode blocks overeager behavior before execution.
- 2026-06-23: Simon Willison discussed Prompt Injection as Role Confusion, a paper showing that models can mistake privileged role-tagged text for user text based on style; the write-up also noted that destyling can significantly reduce attack success.
- 2026-08-08: Boris Cherny said combining model training, input probes, and an intent-checking classifier could reduce unseen indirect prompt injection attacks to near zero in testing.
- 2026-08-10: Boris Cherny described prompt injection as one of the most common attack paths against people and agents, including malicious website text designed to trick agents into revealing credentials.
- 2026-08-24: Claire Vo raised prompt injection as part of a broader product-design question: how agents should handle indexed source data, ephemeral connectors, and user-visible data controls in trustworthy ways.
Relevance to AI PMs
1. Treat connectors and retrieved content as untrusted inputs. If your product reads emails, files, websites, tickets, or shared docs, prompt injection should be in the threat model from day one. PMs should require clear trust boundaries, scoped permissions, and guardrails before enabling autonomous actions.2. Design for containment, not just model compliance. Newsletter coverage repeatedly shows that model-level defenses help but are imperfect. PMs should push for layered controls such as sandboxing, egress restrictions, approval design, tool gating, and blast-radius limits so failures do not become major incidents.
3. Make trust and data flow legible to users. Users need to understand what data is indexed, what is fetched ephemerally, what tools the agent can use, and when external content could affect behavior. Product decisions around visibility, permissions, deletion, and review flows directly influence prompt-injection risk.
Related
- OpenAI: Published design guidance for building agents that resist prompt injection.
- Anthropic / Claude / Claude Opus 4.7 / Claude Code / Mythos Preview: Frequently referenced in discussions of practical defenses, containment, and measured attack success rates.
- Microsoft Copilot Cowork / OneDrive: Example of how connected enterprise surfaces can enable exfiltration paths when prompt injection is combined with sharing and rendering behavior.
- Cline / Adnan Khan: Real-world software supply chain example where prompt injection in workflow inputs led to downstream compromise.
- Role confusion / destyling: Related technical concepts describing why models mis-handle instruction hierarchy and one mitigation approach that reduces attack effectiveness.
- Claire Vo / Boris Cherny / Simon Willison: Recurring commentators highlighting both product-design and technical-defense angles of the problem.
Newsletter Mentions (9)
“#6 𝕏 claire vo 🖤 questioned whether agents can work without indexing source data, how ephemeral connectors and stored data should be presented to users, and how to prevent prompt injection.”
#6 𝕏 claire vo 🖤 questioned whether agents can work without indexing source data, how ephemeral connectors and stored data should be presented to users, and how to prevent prompt injection. She characterized an unnamed harness as immature and lacking user-empathetic evaluation, while noting that self-serve data deletion shipped but promised email follow-up did not occur.
“He described prompt injection as the most common way scammers attack people and agents, including by using malicious website text to trick agents into disclosing credentials.”
𝕏 Boris Cherny shared a prompt-injection benchmark created by an unnamed independent researcher and said Anthropic has largely solved the threat in practice for Claude models, with red-team testing producing similar results. He described prompt injection as the most common way scammers attack people and agents, including by using malicious website text to trick agents into disclosing credentials.
“Boris Cherny said stacking model training, input probes, and an intent-checking classifier can bring indirect prompt injection to ~0 on unseen attacks—a result he did not expect a year ago.”
#6 𝕏 Boris Cherny said stacking model training, input probes, and an intent-checking classifier can bring indirect prompt injection to ~0 on unseen attacks—a result he did not expect a year ago. He also announced that auto mode would become the default in Claude Code the following week.
“Simon Willison Prompt Injection as Role Confusion - Discussion of a paper showing models confuse privileged role-tagged text with user text based on style, enabling serious jailbreaks; the authors demonstrate that 'destyling' text can dramatically reduce attack success.”
This item discusses prompt injection defenses and a specific failure mode called role confusion.
“Telemetry showed users approved ~93% of permission prompts, Claude Code auto mode blocks roughly 83% of overeager behaviors before execution, and Claude Opus 4.7 resists prompt-injection with about 0.1% success on single attempts and ~5–6% after 100 adaptive attempts.”
📝 Anthropic Engineering How we contain Claude across products - Anthropic has deployed Claude across claude.ai, Claude Code, and Claude Cowork while containing blast radius via environment controls (sandboxes, VMs, filesystem/egress limits), model-layer controls (system prompts, classifiers, probes, training), and restricting external-content/tool access, noting Claude Mythos Preview was judged too risky to ship in April 2026. Telemetry showed users approved ~93% of permission prompts, Claude Code auto mode blocks roughly 83% of overeager behaviors before execution, and Claude Opus 4.7 resists prompt-injection with about 0.1% success on single attempts and ~5–6% after 100 adaptive attempts.
“They acknowledge model defenses aren’t perfect—Claude Opus 4.7 shows ≈0.1% attack success on single prompt-injection attempts and ≈5–6% after 100 adaptive attempts—cited Mythos Preview as too high a blast radius to ship in April 2026, and argue combined environment, model, and external-content controls are necessary to cap agents’ blast radius.”
Anthropic ships Claude Code auto mode #1 📝 Anthropic Engineering How we contain Claude across products - Anthropic says it has shipped claude.ai, Claude Code, and Claude Cowork and moved from human-in-the-loop approvals—which users accepted about 93% of the time, producing approval fatigue—toward containment (sandboxes, VMs, egress controls) and automated defenses like Claude Code auto mode, which catches roughly 83% of overeager behaviors. They acknowledge model defenses aren’t perfect—Claude Opus 4.7 shows ≈0.1% attack success on single prompt-injection attempts and ≈5–6% after 100 adaptive attempts—cited Mythos Preview as too high a blast radius to ship in April 2026, and argue combined environment, model, and external-content controls are necessary to cap agents’ blast radius.
“#8 📝 Simon Willison Microsoft Copilot Cowork Exfiltrates Files - A report describes how Microsoft Copilot Cowork allowed agent-sent emails to leak data via externally rendered images and pre-authenticated OneDrive links, creating a path for prompt-injection exfiltration.”
#8 📝 Simon Willison Microsoft Copilot Cowork Exfiltrates Files - A report describes how Microsoft Copilot Cowork allowed agent-sent emails to leak data via externally rendered images and pre-authenticated OneDrive links, creating a path for prompt-injection exfiltration. The post highlights the continued challenge of designing agentic systems that don't enable attackers to extract sensitive data.
“Designing AI agents to resist prompt injection - This post describes techniques for designing AI agents that are robust against prompt injection attacks, outlining security practices and mitigations.”
Today's top 25 insights for PM Builders, ranked by relevance from Blogs, X, LinkedIn, and YouTube. #10 𝕏 Google Research partnered with @BIDMC_Medicine to pilot AMIE, a conversational AI for clinical reasoning, and in a real-world study found it to be safe, feasible, and well-received by patients. #11 📝 OpenAI News Designing AI agents to resist prompt injection - This post describes techniques for designing AI agents that are robust against prompt injection attacks, outlining security practices and mitigations. It focuses on architecture and behavioral approaches to reduce the risk of maliciously crafted inputs influencing agent behavior.
“#19 📝 Simon Willison Clinejection — Compromising Cline’s Production Releases just by Prompting an Issue Triager - Adnan Khan details an attack chain where a prompt injection in a GitHub issue title against an AI-powered triage workflow led to a cache poisoning attack that allowed publishing malicious NPM releases.”
GenAI PM Daily March 07, 2026 GenAI PM Daily 🎧 Listen to this brief 3 min listen Today's top 25 insights for PM Builders, ranked by relevance from LinkedIn, YouTube, X, and Blogs. #18 📝 Simon Willison Agentic manual testing - A guide explaining that coding agents' defining capability is executing the code they write, and emphasizing the necessity of running generated code to verify correctness. The post argues that agents can iterate until code works, but humans should not assume generated code functions without execution. #19 📝 Simon Willison Clinejection — Compromising Cline’s Production Releases just by Prompting an Issue Triager - Adnan Khan details an attack chain where a prompt injection in a GitHub issue title against an AI-powered triage workflow led to a cache poisoning attack that allowed publishing malicious NPM releases.
Related
An AI coding assistant environment used for running evaluation skills and agentic workflows. In this issue it is mentioned as a runtime for ai-evals-course material and as an agent in an OpenRouter-like system.
An AI company best known for Claude. It is referenced implicitly through Claude’s memory and Cowork features.
An AI company building frontier models, ChatGPT, and custom inference hardware. Here it is discussed for Jalapeño and ChatGPT Business Premium Seats.
Anthropic’s assistant, discussed here for shared memory across chat and Cowork. The feature is relevant to PMs because it enables cross-task context reuse and user-controlled memory.
An operator or product thinker who raised concerns about data indexing, connector visibility, prompt injection, and evaluation quality. Her comment focuses on trust, deletion, and user-empathetic system design.
An AI practitioner mentioned for discussing cybersecurity refusals and an unspecified system called Fable. He is cited as the source of a safety-related update.
A Claude model version referenced for its prompt-injection resistance metrics. It serves as a benchmark example of model-layer defenses being strong but not sufficient on their own.
Stay updated on prompt injection
Get curated AI PM insights delivered daily — covering this and 1,000+ other sources.
Subscribe Free