Smart search ranks by meaning as well as keywords (one row per story, last 45 days).
Proofpoint reports cybercriminals are now adopting indirect prompt injection attacks against AI-powered systems.
Proofpoint's threat intelligence reports that cybercriminals have turned to indirect prompt injection attacks, extending the technique from a research concern into observed criminal tradecraft. The article is available by title only, so specific victims, campaigns, and targets are not detailed here.
Hidden prompt injections embedded in documents and metadata can hijack autonomous AI agents, causing data exfiltration and out-of-policy actions at machine speed.
Bowbridge warns that hidden indirect prompt injections, embedded in documents, metadata, emails, images, and code repositories, can cause autonomous AI agents to treat attacker-controlled content as trusted guidance. Because agents inherit user privileges, act silently, and lack human judgment, injections can lead to data exfiltration or file poisoning that traditional security controls cannot detect. A real-world example involved a supplier quote whose metadata instructed an agent to override guidance and select the most expensive option. Bowbridge recommends scanning documents before agents process them.
Researchers unveil Repeat-After-Me, a black-box visual prompt injection achieving over 80% success on Qwen3.6-27B and 47% on GPT-5.5.
Researchers present Repeat-After-Me, a black-box adaptive visual prompt injection that induces frontier VLMs to reveal PII or make malicious tool calls via injected images. It exceeds 80% attack success rate on Qwen3.6-27B and 47% on GPT-5.5 even when the benign user prompt is unrelated and does not authorize the injected task. In a real-world OpenClaw Discord deployment, a minimally injected image can overwrite TOOLS.md, enabling later remote code execution and secret exfiltration.
Mindgard found a prompt injection flaw in Amazon Kiro IDE letting attacker-controlled workspace files exfiltrate sensitive local data; fixed in version 0.8.140.
Mindgard disclosed a prompt injection flaw in Amazon Kiro, an agentic AI IDE, that lets attacker-controlled repository content steer the agent into exfiltrating sensitive workspace data through Kiro Powers, which bundles MCP server configurations, POWER.md steering files, hooks, and contextual knowledge. Exploitation requires the user to open a malicious project via a workspace file and send any message to the agent; difficulty is rated low and it works in both trusted and untrusted workspaces. Amazon fixed the issue in Kiro IDE 0.8.140; the flaw has no CVE identifier and follows earlier Kiro bugs including CVE-2026-10591, plus related prompt-injection and code-execution issues in Codex CLI, Cursor, Gemini CLI, Copilot CLI, and Claude Code.
ActGuard audits LLM agent actions before execution against predicted tool priors, masking only malicious spans from indirect prompt injections while preserving utility.
ActGuard is a pre-execution action auditing framework against indirect prompt injection in LLM agents, judging whether external content causes the current action to deviate from a locally reasonable expectation rather than whether content is inherently suspicious. At each step it predicts the tools likely used by the upcoming action, builds a local tool prior, then performs tool-level contrastive analysis and parameter-level evidence localization to identify deviations. A verifier masks only spans confirmed as malicious and regenerates the action from the sanitized context. On challenging tool-using agent benchmarks it reduces attack success to state-of-the-art levels while keeping task utility close to the no-attack setting; code is publicly available on GitHub.
Researchers frame indirect prompt injection as test-time search, showing added attacker compute improves vulnerability discovery and exploitation against tool-using agents.
The paper models indirect prompt injection as a test-time search over a task-dependent attack surface shaped by the environment, user task, and injection goal. The authors build an agentic attacker with a dedicated search harness that performs reconnaissance, structured strategy reasoning, and adaptive evaluation using victim-agent feedback. Experiments show more attacker test-time compute improves discovery and exploitation of injection vulnerabilities, with explicit strategy management needed to avoid redundant search. The results argue that agentic security evaluations should characterize attacker search procedures and compute budgets rather than treating attack success as budget-independent.
Researcher wunderwuzzi showed Claude Code can be hijacked via prompt injection simply by asking it to summarize a website.
Security researcher Johann Rehberger (wunderwuzzi) demonstrated that Claude Code can be manipulated through prompt injection by simply asking it to summarize a website. Instructions embedded in fetched web content are executed by the agent, hijacking its behavior. The Register frames the finding as another demonstration of prompt injection risks in agentic coding tools that ingest untrusted web content.
A judge banned a plaintiff from electronic court filings after hidden prompt-injection text was discovered planted in legal documents.
Bruce Schneier's blog discusses an incident in which hidden prompt-injection instructions were planted inside a legal filing, apparently targeting AI systems that might process court documents. Judge Walter Spader Jr. responded by banning the plaintiff from electronic filings, requiring all future submissions as printed hard copies. Commenters debate whether the tactic could affect future AI-based processing of court records and whether plain-text formats will regain favor.
Unit 42 PoC shows indirect prompt injection can poison Amazon Bedrock Agent long-term memory, enabling silent exfiltration of conversation history across future sessions.
Palo Alto Networks Unit 42 published a proof of concept showing that indirect prompt injection can silently poison the long-term memory of Amazon Bedrock Agents when the memory feature is enabled. Malicious content on a webpage or document manipulates the agent's session summarization process, so injected instructions persist across sessions and are added to later orchestration prompts, silently exfiltrating user conversation history. The issue is not a vulnerability in the Amazon Bedrock platform but an illustration of the broader unsolved LLM prompt-injection challenge. Amazon reviewed the research and stated that Bedrock Guardrails with the prompt-attack policy provides effective mitigation.
Verifiable Action Card architecture blocks indirect prompt injection in agentic browsers, cutting attack success from 68-100% to 0%.
Researchers propose VAC, a browser-architecture defense that reconstructs approval prompts from the ground-truth pending action and trusted intent provenance, rendering them out-of-band in trusted browser chrome. On a 24-scenario benchmark covering confused-deputy attacks, dialog forging, and indirect prompt injection, attack success fell from 68-100% to 0% across evaluated LLMs, with 78% legitimate-task completion and a 0% false-block rate. Approval is bound to the exact action re-verified at dispatch.
CSO Online publishes a practical penetration-testing guide for GenAI, LLM, and RAG applications, covering prompt injection, retrieval poisoning, and tenant isolation testing.
The guide frames LLM applications as attack graphs spanning prompts, retrieval layers, vector stores, tools, identities, and downstream APIs, arguing that conventional web testing misses instruction-vs-data channel risks. It builds on OWASP prompt injection guidance (direct vs. indirect injection) and NIST's 2025 adversarial machine-learning taxonomy, noting that RAG and fine-tuning do not remove injection risk. Recommended practices include documenting trust transitions across components, using canaries and synthetic records to avoid test side effects, running multi-turn and obfuscated injection campaigns, and verifying chains from poisoned documents to observable state changes. It also details testing RAG pipelines via controlled document poisoning across metadata, OCR layers, and code comments, plus cross-tenant isolation checks on retrieved document IDs.
Attackers use AutoIt and an invoice-themed batch file to inject AsyncRAT into Microsoft-signed charmap.exe for stealthy remote access.
Point Wild Threat Intelligence documented a five-stage campaign starting with 'Right-click to open Invoice Details.bat' that launches hidden PowerShell, drops a renamed AutoIt interpreter and encrypted loader into a random Temp folder, and persists via a Startup-folder batch file. The loader decrypts AsyncRAT only in memory and injects it into the Microsoft-signed charmap.exe (Windows Character Map) process, leaving no payload file on disk. The final payload patches AMSI inside the infected process and includes screen-capture code that prepares images for transfer to a command-and-control server at 158[.]51[.]122[.]136:4944.
A Connecticut pro se litigant hid tiny white-font prompt injections in court filings directing AI to favor him; the judge caught it and sanctioned him.
Pro se plaintiff Matthew Elliott hid prompt injection instructions in 3-point white text within filings in his lawsuit against the New York Bariatric Group, instructing any AI model reviewing the document to produce output agreeing with the filing. The hidden text also included joke messages such as a SpongeBob Nosferatu link and notes like 'hi :) I hope you cant see me'. Court staff noticed unusual white space, and Judge Walter Spader Jr. issued a 14-page sanction decision noting the Connecticut court does not use AI to process documents but warning that hidden AI-directed messages threaten the integrity of filings. Elliott described the scheme as an 'audit' of court AI usage, and the judge cited a prior prompt injection incident in a Brazilian court as evidence the practice may spread.
0day Rubbish discloses a CVSS 8.8 shell command injection in core-admin 1.0.164 via ineffective quote escaping, enabling authenticated remote code execution.
0day Rubbish Research Team publicly disclosed a systemic shell command injection (CWE-78) in core-admin 1.0.164 (build 16468). The flaw stems from ineffective quote escaping and scores 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The disclosure does not mention a CVE identifier or observed exploitation in the wild.
Russia-aligned group UAC-0099 embeds GuardBreaker prompt injection in a VBScript comment to make AI malware scanners refuse analysis of a MATCHBOIL loader.
ESET identified a UAC-0099 VBScript used in an early-stage intrusion against a target in Ukraine that hides a safety-triggering comment (a question about building a nuclear weapon) intended to make AI code scanners refuse to continue analysis. The script downloads MATCHBOIL, a loader associated exclusively with UAC-0099, alongside familiar anti-analysis checks for IDA and Wireshark. The technique turns the AI triage process itself into the attack target, risking missed detections or benign misclassification of malicious samples.
A Connecticut litigant hid white-font prompt injections in court filings to sway AI systems; the judge sanctioned him by revoking e-filing privileges.
A self-represented plaintiff hid prompt injection instructions in 3-point white text within court filings, telling any AI model reading the documents to agree with his filings and grant him relief. The judge called it serious litigation abuse and sanctioned him by revoking electronic filing privileges. It is reportedly the first documented prompt injection attack against a US court and the first sanction for attempting one.
Researchers introduce InjectEave, using electromagnetic injection and hardware nonlinearity to induce side-channel leakage and eavesdrop on headphone audio from 30 meters.
An arXiv paper shows electromagnetic injection can actively amplify side-channel leakage: nonlinear hardware such as amplifiers, ADCs, and power converters modulates secret electrical signals onto an injected EM carrier, upconverting low-frequency secrets into measurable EM emissions. By tuning injection frequency and amplitude, an adversary can shape the effective spectrum and entropy of the resulting leakage. The InjectEave attack demonstrated eavesdropping on wired and wireless headphone audio from up to 30 meters and in through-wall scenarios using accessible RF equipment, plus leakage of smart home device power consumption and analog sensor inputs. Case studies show closed-loop eavesdropping and manipulation of landline phone conversations, and the paper discusses mitigations.
O-CMS 1.0.0 has an authenticated OS command injection in the ai_cli_script parameter, letting privileged attackers execute arbitrary commands.
O-CMS version 1.0.0 contains an authenticated OS command injection vulnerability in its AI CLI configuration functionality. An authenticated attacker with sufficient privileges can supply shell metacharacters and extra commands through the ai_cli_script parameter of /admin/settings/save. The attacker-controlled CLI value is then executed when the configured AI provider is tested via /admin/settings/test-ai.
The UK NCSC raised alarms about prompt injection risks in LLM-integrated systems, urging organizations deploying AI to review exposure.
The UK National Cyber Security Centre (NCSC) has raised alarms about prompt injection attacks against systems using large language models. The warning highlights how attackers can manipulate model instructions to bypass safeguards, exfiltrate data, or trigger unintended agent actions. Organizations deploying LLM-based features are advised to assess and mitigate their exposure to this technique.
Pre-registered ablation finds a model verifier stage in an LLM offensive-security agent suppresses findings; removing it eliminated suppression with precision tradeoff.
The paper evaluates a verifier-and-acceptance stage in an LLM-orchestrated offensive-security agent via a pre-registered 20-run confirmatory ablation and a 2x2 factorial study with 40 runs on vulnerable lab targets. Removing the stage eliminated pre-report suppression (median 2 vs 0 findings, p = 0.00003) but reduced model-blinded shipped precision (0.471 vs 0.353, p = 0.0087). Suppression was attributed to the model verifier rather than deterministic acceptance rules, and an instrumented canary recorded zero external contacts in all 60 runs. The full design retained 93.8% of model-adjudicated true candidates but failed its pre-registered non-inferiority floor of 0.90.
Plan injection plants benign-sounding harmful reasoning that steers LLM actors to adversarial actions while evading chain-of-thought monitors.
Researchers show that injecting harmful but benign-sounding plans into an actor model's context causes it to perform adversarial actions while its reasoning passes chain-of-thought monitors, achieving 25-33% monitor evasion rates across benchmarks and scaling to larger models like DeepSeek-R1. Actor models paraphrase injected plans as their own reasoning without attribution. Giving the monitor access to the injected plan dropped detection by up to 50% on the Bio-Math task, with extra thinking tokens spent rationalizing rather than flagging the plan.
Argument injection in mcp-server-kubernetes 3.8.x MCP server could allow AI clients to execute unintended Kubernetes operations.
Exploit-DB entry 52638 documents an argument injection vulnerability in mcp-server-kubernetes version 3.8.x, a Model Context Protocol server that lets AI assistants interact with Kubernetes clusters. Crafted input can inject additional arguments into commands executed by the server, potentially enabling unauthorized operations or command execution against the cluster. This highlights growing security concerns around MCP servers bridging LLM agents and infrastructure.
Vim sign_jump() before v9.2.1090 permits Ex command injection via unescaped buffer names; low-severity patch disclosed by Christian Brabandt.
Christian Brabandt disclosed an Ex command injection vulnerability in Vim's sign_jump() function affecting versions before v9.2.1090, caused by improper neutralization of unescaped buffer names. The issue is rated Low severity and maps to CWE-88 (argument injection) and CWE-94 (code injection). A CVE has been requested but not yet assigned.
QuantaStor 6.8.3.018 has a CVSS 8.8 command injection in its alert-mail command, exploitable via the smtpPassword field.
0day Rubbish Research Team disclosed a command injection (CWE-78) in QuantaStor 6.8.3.018's alert-mail command, reachable through the smtpPassword field. The flaw scores CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No CVE identifier or evidence of active exploitation is mentioned in the disclosure.
Attackers can hide prompts in invisible HTML within emails to manipulate AI email summarizers into producing misleading summaries.
Dark Reading reports that simple HTML invisible to users can manipulate AI-powered email summarizers into generating false or malicious summaries. The technique is a form of prompt injection delivered through hidden email content. It creates risk that decision-makers act on manipulated AI-generated email summaries rather than the actual message content.
AWS and SANS guidance says system prompts are not security controls; enforce user permissions at retrieval time and default-deny every agent tool invocation.
AWS VP Gee Rittenhouse and SANS fellow Eric Johnson, with three AWS security specialists, published agentic AI security guidance for organizations with agents running or under development. They recommend scoping queries to user permissions inside existing RBAC/ABAC systems and filtering results before the model's context window, noting prompts can be bypassed, ignored, or overridden. The guidance warns risk concentrates when one agent holds sensitive data access, external communication, and exposure to untrusted content, the vector for prompt injection, which OWASP ranks as the top AI application threat. It cites IBM 2025 research that ungoverned shadow AI added $670,000 to average breach cost, and prescribes 30-day behavioral baselines, Cedar or Open Policy Agent for default-deny tool invocation, and four-layer containment with automatic circuit breakers.
ZDI disclosed a CVSS 9.8 unauthenticated prompt injection vulnerability in Flowise's CSV agent that allows remote arbitrary code execution.
ZDI published advisory ZDI-26-634 for a prompt injection vulnerability in Flowise's CSV agent component. Remote, unauthenticated attackers can inject prompts to execute arbitrary code on affected installations. ZDI assigned CVSS 9.8 and the issue is tracked as CVE-2026-70477.