<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reflex on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/reflex/</link><description>Recent content in Reflex on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 02 Oct 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/reflex/index.xml" rel="self" type="application/rss+xml"/><item><title>The Shai-Hulud NPM Worm: When Supply Chains Bite Back</title><link>https://javapro-en.svenruppert.com/the-shai-hulud-npm-worm-when-supply-chains-bite-back/</link><pubDate>Thu, 02 Oct 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/the-shai-hulud-npm-worm-when-supply-chains-bite-back/</guid><description>&lt;p&gt;Let’s be clear: Shai-Hulud wasn’t just another npm compromise. For the first time, a &lt;strong&gt;self-propagating worm ripped through the JavaScript supply chain.&lt;/strong&gt; We’ve seen worms before, but this one changed the game. It hijacked developers’ credentials and CI/CD pipelines, transforming them into its attack vector.&lt;/p&gt;
&lt;p&gt;At KCDC and JavaZone, I warned about the dangers of &lt;code&gt;curl | bash | hacked&lt;/code&gt;. Unfortunately, what once looked like a theory (or an occasional exploit) &lt;strong&gt;has now evolved into something far more dangerous.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>