<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cybercrime.club</title><link>https://cybercrime.club/tags/package-manager/</link><description>Infrastructure security news for people who build infrastructure.</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 10:00:00 -0400</lastBuildDate><atom:link href="https://cybercrime.club/tags/package-manager/" rel="self" type="application/rss+xml"/><item><title>Worms All the Way Down: Why npm and PyPI Will Keep Spawning Self-Propagating Compromises Until We Re-Architect Install-Time Trust</title><link>https://cybercrime.club/deep-dives/install-time-execution-npm-worm-lineage-2026/</link><pubDate>Sun, 10 May 2026 10:00:00 -0400</pubDate><guid>https://cybercrime.club/deep-dives/install-time-execution-npm-worm-lineage-2026/</guid><description>From the original Shai-Hulud in September 2025 through CanisterSprawl, the Bitwarden CLI compromise, and Mini Shai-Hulud, every major npm/PyPI worm of the last eight months has used the same primitive: package lifecycle hooks that run arbitrary code on install. Until the registries change that default, each generation will keep landing.</description></item></channel></rss>