this may be the worst one

A new npm supply-chain attack dubbed “Shy Halude” is spreading far beyond the usual pattern of stealing tokens from a single victim. Instead of waiting for an end user to install a malicious package and then running a post-install script locally, the malware appears to propagate from repository to repository—then repeatedly publishes updated “patch” versions—so the compromise can keep expanding as long as automated dependency updates keep pulling in the infected releases.

The incident is framed as part of a broader hacking spree, with the transcript linking it to the recently reported “Singularity NX” hack. Both attacks rely on the same general mechanism: a compromised package version triggers a post-install step that harvests credentials. But Shy Halude’s twist is operational. After harvesting tokens, it doesn’t merely exfiltrate them to a public place; it immediately uses them to interact with GitHub—updating CI workflows, adding new post-install behavior, and pushing further npm package updates. That creates a self-propagating loop: if an attacker compromises one repository during CI, the next round can infect additional repositories, including those whose CI systems hold the same kinds of tokens.

The likely entry point is described as a phishing-driven compromise of a small repository. A deprecated package—identified as “RX NT authentication”—had not seen publications for a long time, then suddenly released new versions (including 005 and 006) containing the malicious payload. The transcript emphasizes how the attack leverages patch-version updates, warning that “autoupgrade patch versions” can turn a single malicious release into a rapid, organization-wide rollout. The core advice is blunt: lock dependency versions, stop relying on automatic patch upgrades, and treat dependency automation as a risk multiplier.

As the compromise spreads, the number of affected npm packages is reported to have risen quickly—from about 40 to roughly 180 within hours—suggesting an accelerating growth curve. The transcript also highlights high-profile collateral: CrowdStrike is mentioned as being affected, with an ironic juxtaposition between its security branding and its role as a distributor in the worm-like incident. Another example cited is Tiny Color, where earlier versions are described as compromised and later versions (notably “420”) are presented as the safe line.

The broader takeaway is not just “patch the immediate package.” Even after fixing one dependency, downstream projects remain exposed if their dependency graph still includes compromised transitive packages or if other components (like CI tokens and automation) enable the attacker’s propagation. The transcript closes with a call to reduce dependency sprawl—question whether large dependency trees are necessary—arguing that simpler, smaller code paths can reduce the compounding blast radius of future supply-chain attacks.