<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Backdoors on No Semicolons</title><link>https://nosemicolons.com/tags/ai-backdoors/</link><description>Recent content in AI Backdoors on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 30 Sep 2026 14:27:34 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/ai-backdoors/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Prompt Injection Backdoor: How Compromised Dependencies Are Rewriting Your Generated Functions</title><link>https://nosemicolons.com/posts/ai-code-generation-prompt-injection-backdoor-compromised-dependencies/</link><pubDate>Wed, 30 Sep 2026 14:27:34 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-prompt-injection-backdoor-compromised-dependencies/</guid><description>&lt;p>Ever noticed your AI assistant suggesting slightly different code patterns after installing a new package? What if I told you that innocent-looking dependency might be actively manipulating your AI&amp;rsquo;s responses to inject backdoors into your codebase?&lt;/p>
&lt;p>I stumbled onto this rabbit hole last month while debugging what seemed like a simple authentication bug. The AI-generated login function looked clean, worked perfectly in testing, but had a subtle backdoor that I almost missed entirely. The culprit? A compromised npm package that was literally teaching my AI to write vulnerable code.&lt;/p></description></item></channel></rss>