Tag
8 articles tagged Prompt Injection.
AI Security
Cursor, GitHub Copilot, Claude Desktop, Codex, and VS Code all embed a browser and give it powers a normal browser withholds. Forever Security showed how a hostile page turns those powers into code execution, file theft, and address-bar spoofing.
AI Security
Coding agents obey instruction files in the folder you start them in. Start one in ~/Downloads and any web page that can save a file there can give it orders.
AI Security
An agent that remembers can be taught to remember the wrong things. Treat every memory write as a privileged action with provenance, review, and an expiry date.
AI Security
Anything a prompt can influence, an attacker can influence. Here is how to handle model output safely at each place it lands: the browser, the database, the shell, and the interpreter.
AI Security
A system prompt is configuration the user can probably read, not a vault. Here is what to move out of it, where to put it instead, and how to test that it stays out.
AI Security
An AI agent in a GitHub Actions workflow reads attacker-controlled text while holding your tokens. Here is the threat model and a workflow design that keeps a successful prompt injection from reaching secrets.
AI Security
Connecting an MCP server hands its author a voice in your agent's context and, often, code execution on your machine. Here is how to review one before you connect it and keep it honest afterwards.
AI Security
Filters and stern system prompts reduce prompt injection, but they cannot eliminate it. The durable fix is to treat model output as untrusted input and authorize every action it proposes.
