<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: akhil0997</title>
    <description>The latest articles on DEV Community by akhil0997 (@akhil0997).</description>
    <link>https://dev.to/akhil0997</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3890179%2Fe7ed8df8-de65-4412-95a0-a43f70612612.jpeg</url>
      <title>DEV Community: akhil0997</title>
      <link>https://dev.to/akhil0997</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/akhil0997"/>
    <language>en</language>
    <item>
      <title>nukon-pi-detect: a tiny, offline prompt-injection scanner for CI pipelines</title>
      <dc:creator>akhil0997</dc:creator>
      <pubDate>Tue, 21 Apr 2026 06:07:45 +0000</pubDate>
      <link>https://dev.to/akhil0997/nukon-pi-detect-a-tiny-offline-prompt-injection-scanner-for-ci-pipelines-32fn</link>
      <guid>https://dev.to/akhil0997/nukon-pi-detect-a-tiny-offline-prompt-injection-scanner-for-ci-pipelines-32fn</guid>
      <description>&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;Most teams shipping LLM features test for code bugs but not for &lt;br&gt;
prompt-injection attacks in their inputs. They rely on the model's &lt;br&gt;
built-in safety. That's not a plan.&lt;/p&gt;
&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;nukon-pi-detect is a tiny Python library + CLI that scans strings and &lt;br&gt;
files for known prompt-injection patterns before they reach your model.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install &lt;/span&gt;nukon-pi-detect
nukon-pi-detect scan &lt;span class="nt"&gt;--string&lt;/span&gt; &lt;span class="s2"&gt;"ignore previous instructions"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What it catches
&lt;/h2&gt;

&lt;p&gt;48 curated patterns across 5 categories:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Classic injection ("ignore previous instructions" and variants)&lt;/li&gt;
&lt;li&gt;Jailbreaks (DAN, STAN, AIM, grandma exploit, dual-response trick)&lt;/li&gt;
&lt;li&gt;Delimiter escapes (ChatML tokens, fake  tags, [INST] hijacks)&lt;/li&gt;
&lt;li&gt;Unicode smuggling (invisible tag chars in U+E00xx, bidi overrides, homoglyphs)&lt;/li&gt;
&lt;li&gt;Indirect injection (payloads targeting downstream LLM summarizers)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What makes it different
&lt;/h2&gt;

&lt;p&gt;Fully deterministic - regex + Unicode codepoint checks. No ML, no &lt;br&gt;
network calls, no API keys. Under 1ms per scan. Zero runtime dependencies.&lt;/p&gt;

&lt;p&gt;Exit code 2 on MALICIOUS so it fails CI builds by default.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't do
&lt;/h2&gt;

&lt;p&gt;It won't catch novel attacks. It's not a runtime policy engine. It &lt;br&gt;
catches the 80% - the known-known attacks in every red-team dataset.&lt;/p&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;GitHub: &lt;a href="https://github.com/akhil0997/nukon-pi-detect" rel="noopener noreferrer"&gt;https://github.com/akhil0997/nukon-pi-detect&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;PyPI: &lt;a href="https://pypi.org/project/nukon-pi-detect" rel="noopener noreferrer"&gt;https://pypi.org/project/nukon-pi-detect&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Apache 2.0. Pattern submissions welcome.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>python</category>
      <category>security</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
