<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Npm on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/npm/</link><description>Recent content in Npm on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 11 Jun 2026 12:08:30 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/npm/index.xml" rel="self" type="application/rss+xml"/><item><title>The Miasma Worm Hid in Microsoft's Code and Ran the Moment You Opened It</title><link>https://hackingpassion.com/miasma-worm-ai-coding-agents/</link><pubDate>Thu, 11 Jun 2026 12:08:30 +0200</pubDate><guid>https://hackingpassion.com/miasma-worm-ai-coding-agents/</guid><description>&lt;p>GitHub disabled &lt;strong>73 of Microsoft&amp;rsquo;s own repositories in 105 seconds&lt;/strong>, after a worm called &lt;strong>Miasma&lt;/strong> planted a credential stealer inside Microsoft&amp;rsquo;s Azure code on GitHub.&lt;/p>
&lt;p>The part that makes this different is how it ran. A developer did not need to build the project or install a package. &lt;strong>Opening one of those repositories in an AI editor, VS Code, Claude Code, Cursor, or Gemini, was enough to set it off.&lt;/strong> 😱&lt;/p></description></item><item><title>Bitwarden CLI Backdoored on npm for 93 Minutes</title><link>https://hackingpassion.com/bitwarden-cli-supply-chain-attack/</link><pubDate>Fri, 24 Apr 2026 11:30:31 +0200</pubDate><guid>https://hackingpassion.com/bitwarden-cli-supply-chain-attack/</guid><description>&lt;p>Bitwarden&amp;rsquo;s CLI was backdoored and pushed to npm on April 22, 2026. It was live for &lt;strong>93 minutes&lt;/strong>. Every developer who installed it during that window has to treat their &lt;strong>entire machine as compromised&lt;/strong>. GitHub tokens, SSH keys, AWS credentials, cloud secrets. All of it.&lt;/p>
&lt;p>If you followed the Shai-Hulud story back in November 2025, this will sound familiar. That attack spread through npm and hit packages from Zapier, Postman, PostHog, and hundreds of others. &lt;strong>132 million monthly downloads affected.&lt;/strong> Stolen credentials dumped into public GitHub repositories for anyone to find. This new attack names itself &lt;strong>Shai-Hulud: The Third Coming&lt;/strong>, after the giant sandworms from Frank Herbert&amp;rsquo;s Dune. The irony is that this third wave specifically targets AI tools.&lt;/p></description></item><item><title>Axios npm Supply Chain Attack: How a Fake Meeting Compromised 100 Million Downloads</title><link>https://hackingpassion.com/axios-npm-supply-chain-attack/</link><pubDate>Sat, 04 Apr 2026 13:50:24 +0200</pubDate><guid>https://hackingpassion.com/axios-npm-supply-chain-attack/</guid><description>&lt;p>Axios, the JavaScript library with over &lt;strong>100 million weekly downloads&lt;/strong>, was compromised on March 31st. For roughly three hours, every fresh install of those two versions silently dropped a &lt;strong>remote access trojan&lt;/strong> on the machine that ran it. Windows, macOS, and Linux, all targeted. The installation completed normally, nothing flagged the change, and the backdoor was already running by the time the command finished. 😏&lt;/p>
&lt;p>Axios is a JavaScript HTTP client that developers use to send web requests from their applications. It ships inside frontend frameworks, backend services, mobile apps, and &lt;strong>CI/CD pipelines&lt;/strong>, and if a company runs Node.js anywhere in their stack, Axios is almost certainly somewhere in that dependency tree. That is what made this attack so significant.&lt;/p></description></item></channel></rss>