<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Shai-Hulud on CybersecurityOS</title><link>http://www.cybersecurityos.net/tags/shai-hulud/</link><description>Recent content in Shai-Hulud on CybersecurityOS</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 04 Aug 2026 11:15:15 -0500</lastBuildDate><atom:link href="http://www.cybersecurityos.net/tags/shai-hulud/index.xml" rel="self" type="application/rss+xml"/><item><title>The keyv Worm Turned Credential Rotation Into a Trigger. Your Playbook Needs a New First Step.</title><link>http://www.cybersecurityos.net/posts/devsecops/keyv-npm-worm-supply-chain-defense/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><guid>http://www.cybersecurityos.net/posts/devsecops/keyv-npm-worm-supply-chain-defense/</guid><description>&lt;p&gt;On August 4, 2026, a developer somewhere ran &lt;code&gt;npm install&lt;/code&gt;. Before a single line of their own code executed, a worm had already read their AWS keys, their npm token, their GitHub credentials, and the secrets sitting in their CI runner&amp;rsquo;s memory. Then it used those credentials to publish poisoned versions of every package it could reach — at roughly one package per second.&lt;/p&gt;
&lt;p&gt;&lt;img src="http://www.cybersecurityos.net/posts/devsecops/images/keyv-npm-worm-hero.svg" alt="The keyv Worm Turned Credential Rotation Into a Trigger"&gt;&lt;/p&gt;</description></item></channel></rss>