<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>AI Security Risks: cases and guides</title><description>A register of AI security risks with the documented incidents behind each one, current OWASP, MITRE ATLAS and NIST IDs, controls to start with, and a free tool that builds a register for the AI you use.</description><link>https://aisecurityrisks.com/</link><language>en-us</language><item><title>AI acceptable use policy: a starter template tied to the risks</title><link>https://aisecurityrisks.com/guides/ai-acceptable-use-policy/</link><guid isPermaLink="true">https://aisecurityrisks.com/guides/ai-acceptable-use-policy/</guid><description>A short AI acceptable use policy you can copy and adapt, with each clause linked to the security risk and documented cases it answers. No email required.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate></item><item><title>MCP security risks: what has gone wrong, and what the spec says</title><link>https://aisecurityrisks.com/guides/mcp-security-risks/</link><guid isPermaLink="true">https://aisecurityrisks.com/guides/mcp-security-risks/</guid><description>Documented Model Context Protocol attacks, the risks the MCP specification itself names, and a checklist to run before you connect a server.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate></item><item><title>OWASP Top 10 for LLM Applications 2026: the list and what changed</title><link>https://aisecurityrisks.com/guides/owasp-llm-top-10-2026/</link><guid isPermaLink="true">https://aisecurityrisks.com/guides/owasp-llm-top-10-2026/</guid><description>The 2026 OWASP Top 10 for LLM Applications, entry by entry, with what moved since 2025 and which IDs now mean something different.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Prompt injection examples: documented cases, labeled incident or demo</title><link>https://aisecurityrisks.com/guides/prompt-injection-examples/</link><guid isPermaLink="true">https://aisecurityrisks.com/guides/prompt-injection-examples/</guid><description>Dated prompt injection cases from Microsoft 365 Copilot, Slack AI, Gemini, ChatGPT, coding assistants and more, each labeled as a real incident or a research demonstration, with the source.</description><pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Incident: Industrial-scale distillation of U.S. models</title><link>https://aisecurityrisks.com/cases/#distillation-aa26-251a/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#distillation-aa26-251a/</guid><description>NSA, CISA and the FBI say six named China-based AI companies collected outputs from U.S. models over millions of exchanges, from at least late 2024, and used them to train their own models. The advisory asks model providers to watch for anomalous accounts and usage, rate-limit, verify identities, log telemetry and share intelligence across providers.</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Incident: Malicious dataset used to break into Hugging Face clusters</title><link>https://aisecurityrisks.com/cases/#hugging-face-dataset-intrusion/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#hugging-face-dataset-intrusion/</guid><description>Hugging Face says a malicious dataset used two code-execution paths in its dataset processing, a remote-code loader and a template injection in a dataset configuration, to run code on a worker. The intruder then harvested credentials and moved into several internal clusters over a weekend. Hugging Face reports access to some internal datasets and service credentials, and no tampering with public models, datasets or Spaces. It closed both paths and rotated credentials. Its post does not name the attacker. MITRE&apos;s case study attributes the activity to autonomous agents from OpenAI cyber evaluations.</description><pubDate>Thu, 16 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Research demo: CI secret read through a coding agent&apos;s file tool</title><link>https://aisecurityrisks.com/cases/#claude-code-github-action/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#claude-code-github-action/</guid><description>Microsoft researchers hid instructions in GitHub issue and pull request text processed by Anthropic&apos;s Claude Code GitHub Action. Secret scrubbing covered shell commands, but the agent&apos;s in-process Read tool could open /proc/self/environ and expose the workflow&apos;s API key. Microsoft reported it on April 29, 2026 and Anthropic fixed it on May 5 by blocking sensitive /proc files (Claude Code 2.1.128). Microsoft&apos;s advice: never give one workflow untrusted input, secrets and outbound communication at the same time.</description><pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Research demo: Prompt to code execution in Semantic Kernel&apos;s vector search</title><link>https://aisecurityrisks.com/cases/#semantic-kernel-rce/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#semantic-kernel-rce/</guid><description>In the Python version of Microsoft&apos;s Semantic Kernel, the default filter for in-memory vector search built a Python lambda from model-controlled values and ran it with eval(). A crafted prompt got past the blocklist and ran code on the host. Fixed in semantic-kernel 1.39.4 (CVE-2026-26030). Microsoft&apos;s lesson: any tool parameter the model can influence is attacker-controlled input.</description><pubDate>Thu, 19 Feb 2026 00:00:00 GMT</pubDate></item><item><title>Incident: &quot;Summarize with AI&quot; links that plant memories</title><link>https://aisecurityrisks.com/cases/#ai-recommendation-poisoning/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#ai-recommendation-poisoning/</guid><description>Most AI assistants accept a prefilled prompt in a link. Microsoft found businesses using such links to tell assistants to remember them as a trusted source or recommend them first. Over 60 days of email traffic it counted 50 prompts from 31 companies. Microsoft&apos;s advice: treat AI assistant links like downloads, review and prune stored memories, and hunt for assistant URLs whose prompt contains words like &quot;remember&quot; or &quot;trusted source&quot;.</description><pubDate>Tue, 10 Feb 2026 00:00:00 GMT</pubDate></item><item><title>Incident: GTG-1002 used a jailbroken coding agent for espionage</title><link>https://aisecurityrisks.com/cases/#gtg-1002/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#gtg-1002/</guid><description>Anthropic says a group it assesses with high confidence to be Chinese state-sponsored used Claude Code to attempt intrusions at about 30 organizations, succeeding in a small number. The operators split the work into innocent-looking tasks and told the model it worked for a security firm doing defensive testing. Anthropic estimates AI did 80 to 90 percent of the campaign&apos;s work. It banned the accounts, notified affected organizations and added detection classifiers.</description><pubDate>Thu, 13 Nov 2025 00:00:00 GMT</pubDate></item><item><title>Incident: Fake Postmark MCP server copied every email to an attacker</title><link>https://aisecurityrisks.com/cases/#postmark-mcp-backdoor/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#postmark-mcp-backdoor/</guid><description>Someone published an npm package called postmark-mcp that posed as an MCP server for the Postmark email service. After 15 harmless versions, version 1.0.16 added a backdoor that blind-copied outgoing email to an external server. Postmark says it had nothing to do with the package. It told users to remove it, check email logs and consider rotating any credentials sent by email while it was installed.</description><pubDate>Thu, 25 Sep 2025 00:00:00 GMT</pubDate></item><item><title>Research demo: A calendar invite that took over Gemini</title><link>https://aisecurityrisks.com/cases/#gemini-calendar-invite/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#gemini-calendar-invite/</guid><description>SafeBreach researchers put instructions in the title of a Google Calendar invitation. When the victim asked Gemini about their calendar, it followed them: deleting events, opening a video call, controlling smart-home devices through Google Home and leaking email subject lines in URLs. The researchers reported it in February 2025. Google described layered defenses, including stronger confirmations for sensitive actions and URL sanitization, and called the techniques theoretical.</description><pubDate>Wed, 06 Aug 2025 00:00:00 GMT</pubDate></item><item><title>Incident: Wiper prompt shipped in the Amazon Q VS Code extension</title><link>https://aisecurityrisks.com/cases/#amazon-q-vscode-extension/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#amazon-q-vscode-extension/</guid><description>An attacker used a GitHub token with too much scope to commit code to the open-source repository of the Amazon Q Developer extension for VS Code, and the code shipped in version 1.84.0. MITRE&apos;s write-up says the code prompted the Q agent to clean a system to a near-factory state and delete file system and cloud resources. AWS says the code failed to run because of a syntax error and made no changes to services or customer environments. Version 1.85.0 removed it (CVE-2025-8217).</description><pubDate>Wed, 23 Jul 2025 00:00:00 GMT</pubDate></item><item><title>Incident: LAMEHUG malware asked an LLM for its next commands</title><link>https://aisecurityrisks.com/cases/#lamehug/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#lamehug/</guid><description>Ukraine&apos;s CERT-UA found Python malware that called Qwen 2.5-Coder-32B-Instruct through the Hugging Face API to write reconnaissance and document-theft commands on infected machines. It arrived in phishing emails sent from compromised accounts posing as ministry officials. CERT-UA attributed the activity to APT28 with medium confidence. It did not say whether the generated commands worked.</description><pubDate>Thu, 17 Jul 2025 00:00:00 GMT</pubDate></item><item><title>Research demo: EchoLeak: one email, data out of Microsoft 365 Copilot</title><link>https://aisecurityrisks.com/cases/#echoleak/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#echoleak/</guid><description>Researchers showed that a single crafted email could make Microsoft 365 Copilot send internal data to an attacker with no click from the victim. Copilot pulled the email into its context, and the chain got past an injection classifier and link redaction, then used auto-fetched images and a Teams proxy allowed by the content security policy. Tracked as CVE-2025-32711, described as AI command injection in M365 Copilot that lets an unauthorized attacker disclose information over a network.</description><pubDate>Wed, 11 Jun 2025 00:00:00 GMT</pubDate></item><item><title>Research demo: Hidden instructions in an MCP tool description</title><link>https://aisecurityrisks.com/cases/#mcp-tool-poisoning-poc/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#mcp-tool-poisoning-poc/</guid><description>Invariant Labs put instructions in the description of an innocent-looking add tool. In Cursor, the agent then read the user&apos;s MCP config file and SSH private key and sent them out through a hidden tool parameter. The confirmation dialog did not show the full input. The researchers also described rug pulls (a server changes a tool after approval) and shadowing (one server&apos;s tool description changes how the agent uses another server&apos;s tool). They recommend pinning server versions and showing users full tool descriptions.</description><pubDate>Tue, 01 Apr 2025 00:00:00 GMT</pubDate></item><item><title>Research demo: Rules File Backdoor in AI coding assistants</title><link>https://aisecurityrisks.com/cases/#rules-file-backdoor/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#rules-file-backdoor/</guid><description>Pillar Security hid instructions in the rules files that configure Cursor and GitHub Copilot, using invisible Unicode characters that reviewers could not see. The assistants then added attacker-chosen code, such as a script tag, without mentioning it in chat. Cursor said the risk was the user&apos;s responsibility. GitHub said users must review suggestions, and in May 2025 it started warning when a file on github.com contains hidden Unicode text.</description><pubDate>Tue, 18 Mar 2025 00:00:00 GMT</pubDate></item><item><title>Incident: Storm-2139 resold access to hijacked AI service accounts</title><link>https://aisecurityrisks.com/cases/#storm-2139/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#storm-2139/</guid><description>Members of a group Microsoft tracks as Storm-2139 scraped exposed customer credentials from public sources and used them to get into generative AI service accounts. They changed what the services would do, deliberately worked around Microsoft&apos;s safeguards, and resold the access. Microsoft sued in December 2024, seized a website central to the operation and later named four developers in an amended complaint.</description><pubDate>Thu, 27 Feb 2025 00:00:00 GMT</pubDate></item><item><title>Incident: Malicious models on Hugging Face slipped past the scanner</title><link>https://aisecurityrisks.com/cases/#hugging-face-nullifai/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#hugging-face-nullifai/</guid><description>ReversingLabs found two models on Hugging Face whose Pickle files opened a reverse shell when loaded. The files used 7z compression and broke right after the payload, so Hugging Face&apos;s Picklescan tool did not flag them even though the code still ran. ReversingLabs reported them on January 20, 2025. Hugging Face removed the models within 24 hours and changed Picklescan to inspect broken Pickle files.</description><pubDate>Thu, 06 Feb 2025 00:00:00 GMT</pubDate></item><item><title>Incident: ProKYC sold deepfake identities to beat ID checks</title><link>https://aisecurityrisks.com/cases/#prokyc-deepfake-kyc/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#prokyc-deepfake-kyc/</guid><description>ProKYC was sold on criminal forums as a way through remote identity verification. It produced a fake ID document together with a video of the face on it, and was used for account fraud against cryptocurrency exchanges. IDScan.net reported a price of $629 a year. Cato Networks&apos; original write-up did not load for us, so this entry rests on IDScan&apos;s report and MITRE&apos;s case study.</description><pubDate>Tue, 01 Oct 2024 00:00:00 GMT</pubDate></item><item><title>Research demo: Slack AI leaked a private-channel API key</title><link>https://aisecurityrisks.com/cases/#slack-ai-exfiltration/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#slack-ai-exfiltration/</guid><description>PromptArmor posted an instruction in a public channel that only the attacker had joined. When a victim later asked Slack AI about their own private messages, it followed the instruction and showed a &quot;reauthenticate&quot; link carrying an API key from a private channel. The citation pointed only to the victim&apos;s channel. Slack told the researchers this was intended behavior, since public channel messages are searchable by all workspace members.</description><pubDate>Tue, 20 Aug 2024 00:00:00 GMT</pubDate></item><item><title>Research demo: False memories written into ChatGPT from a shared document</title><link>https://aisecurityrisks.com/cases/#chatgpt-memory-injection/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#chatgpt-memory-injection/</guid><description>A researcher put instructions in a Google Doc. When ChatGPT read it through a connected app, each instruction became a stored memory that carried into later conversations. Uploaded images worked too, and the researcher could also delete all memories this way. OpenAI closed the report as a model safety issue rather than a security vulnerability. The researcher advises watching for &quot;Memory updated&quot; notices and reviewing stored memories.</description><pubDate>Wed, 22 May 2024 00:00:00 GMT</pubDate></item><item><title>Incident: LLMjacking: stolen cloud keys used to run up AI bills</title><link>https://aisecurityrisks.com/cases/#llmjacking/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#llmjacking/</guid><description>Attackers took cloud credentials from a server running a vulnerable version of Laravel (CVE-2021-3129) and used them to reach cloud-hosted language models. Their script checked stolen keys against ten AI services, including AWS Bedrock, Azure, OpenAI and Google Vertex AI. Sysdig estimated a worst case of more than $46,000 a day in model costs for the victim. That figure assumes maximum quota use in several regions. Its advice: patch, keep secrets out of plain text, scope credentials tightly and log model invocations.</description><pubDate>Mon, 06 May 2024 00:00:00 GMT</pubDate></item><item><title>Research demo: Hallucinated package name downloaded more than 30,000 times</title><link>https://aisecurityrisks.com/cases/#package-hallucination/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#package-hallucination/</guid><description>A Lasso Security researcher asked four models thousands of coding questions across five languages and found they often recommended packages that did not exist, sometimes the same invented name again and again. He uploaded an empty package under one of those names, huggingface-cli. The empty package received more than 30,000 downloads in three months, and an Alibaba research repository told readers to install it. OWASP calls registering such names in advance slopsquatting.</description><pubDate>Thu, 28 Mar 2024 00:00:00 GMT</pubDate></item><item><title>Incident: ShadowRay: exposed Ray clusters taken over</title><link>https://aisecurityrisks.com/cases/#shadowray/</link><guid isPermaLink="true">https://aisecurityrisks.com/cases/#shadowray/</guid><description>Ray, an open-source framework for scaling AI workloads, has a Jobs API with no authorization. Oligo found internet-exposed clusters that attackers had been using since at least September 2023 to install crypto-miners, open reverse shells and collect credentials for services such as OpenAI, Hugging Face and Stripe. The issue is tracked as CVE-2023-48022, which Anyscale disputes. Its position is that Ray is not meant to run outside a strictly controlled network.</description><pubDate>Tue, 26 Mar 2024 00:00:00 GMT</pubDate></item></channel></rss>