<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ics on Inanna Malick</title>
    <link>https://recursion.wtf/tags/ics/</link>
    <description>Recent content in Ics on Inanna Malick</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 25 Feb 2026 12:00:00 -0800</lastBuildDate>
    <atom:link href="https://recursion.wtf/tags/ics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vibe Coding Against Critical Infrastructure</title>
      <link>https://recursion.wtf/posts/vibe_coding_critical_infrastructure/</link>
      <pubDate>Wed, 25 Feb 2026 12:00:00 -0800</pubDate>
      <guid>https://recursion.wtf/posts/vibe_coding_critical_infrastructure/</guid>
      <description>&lt;p&gt;This post describes a threat model: malicious vibe coding at scale targeting vulnerable Industrial Control Systems (ICS)&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;, with jailbroken LLMs leveraging their understanding of holistic process interaction to bypass safety controls using tools already present on the target system. The formula: frontier models + agentic loops + malicious persona basins + swarming attacks. At scale, it doesn&amp;rsquo;t matter if the success rate is 1/20 or 1/100, that&amp;rsquo;s still enough to cause serious harm.&lt;/p&gt;&#xA;&lt;p&gt;This post is split into three main segments:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;proof of malicious intent&lt;/li&gt;&#xA;&lt;li&gt;proof of capability&lt;/li&gt;&#xA;&lt;li&gt;the threat model&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;As you read, keep in mind that the threat is probabilistic: imagine a swarm of malicious Claude Code-like agents running in a gastown&lt;sup id=&#34;fnref:2&#34;&gt;&lt;a href=&#34;#fn:2&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;2&lt;/a&gt;&lt;/sup&gt;-like environment, spawning workers to attack IPs as they are discovered. In my tests against &lt;a href=&#34;https://tryhackme.com&#34;&gt;tryhackme.com&lt;/a&gt;&lt;sup id=&#34;fnref:3&#34;&gt;&lt;a href=&#34;#fn:3&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;3&lt;/a&gt;&lt;/sup&gt; boxes, I ran 3 parallel attackers in such a swarm architecture, because that&amp;rsquo;s the number of boxes I could stand up at any given time. Real attackers would only be constrained by their subscription plan limits.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Today we were unlucky, but remember, we only have to be lucky once - you will have to be lucky always&lt;/p&gt;&#xA;&lt;p&gt;— the Provisional Irish Republican Army&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;Massive thanks to &lt;a href=&#34;https://bsky.app/profile/hacks4pancakes.com&#34;&gt;@hacks4pancakes&lt;/a&gt; for their help in refining the ICS terminology in this post via &lt;a href=&#34;https://bsky.app/profile/hacks4pancakes.com/post/3mfpqxykxas23&#34;&gt;discussion on bluesky&lt;/a&gt;. All errors are mine.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
