XeniCore

Tag: npm

  • Shai-Hulud: When Trust in npm Becomes the Attack Surface

    Modern JavaScript development runs on an assumption that rarely gets questioned:
    dependencies are safe by default.

    Every npm install pulls code written by strangers, maintained at unknown cadence, and executed automatically in trusted environments. The Shai-Hulud npm campaigns did not exploit a vulnerability in npm itself. They exploited belief – belief that widely used ecosystems self-regulate.

    This was not a smash-and-grab operation.
    It was a slow poisoning of trust, designed to persist quietly inside developer workflows and CI/CD pipelines.

    (more…)

  • Shai-Hulud Weaponisation of npm’s Trust Model

    In our ongoing analysis of supply chain compromises, we’ve examined how attackers exploit the fundamental trust relationships that power modern software development. From dependency confusion attacks to compromised build systems, threat actors have consistently demonstrated that the most devastating breaches don’t break through defences—they walk through open doors marked “trusted.”

    On September 23, 2025, the Cybersecurity and Infrastructure Security Agency (CISA) issued an alert that crystallises this threat: a self-replicating worm named “Shai-Hulud” has compromised over 500 packages in the npm ecosystem, the world’s largest JavaScript registry. This isn’t merely another supply chain attack; it’s a systematic exploitation of the trust architecture that underpins modern web development.

    The significance of this compromise extends far beyond its immediate impact. Shai-Hulud represents an evolution in supply chain attacks—from opportunistic package poisoning to automated, self-propagating ecosystem compromise. To understand why this attack succeeded so spectacularly, and how to defend against its successors, we must examine how it weaponised the very mechanisms designed to make software development seamless.

    (more…)