Trapdex Subscribe

CampaignsPublisher / pipeline compromise

Shai-Hulud 2.0 ('Sha1-Hulud: The Second Coming') self-propagating npm worm

Do this now

  1. Search lockfiles and caches for setup_bun.js or bun_environment.js
  2. Look for repos described as 'Sha1-Hulud' and for runners named SHA1HULUD in your orgs
  3. Rotate npm, GitHub and cloud credentials on any host or runner that installed affected versions
  4. Block install scripts or enforce a minimum release age in CI

Indicators

For blocklists and log searches. All values are defanged.

  • sha2563

CSVJSONAll 3 indicators

What happened

A worm spread through npm using stolen maintainer tokens. Each infected package gained a preinstall hook that runs a Bun-based stealer, which posts developer, CI and cloud credentials to public GitHub repos and registers infected hosts as self-hosted runners. Datadog counted 796 backdoored packages with more than 20M weekly downloads.

  • npm
  • GitHub
  • GitHub Actions

Attack chain

  1. Lure

    No phishing lure documented; developers and CI installed trojanized releases of trusted packages

    First seen

  2. Artifact

    Trojanized npm versions with preinstall setup_bun.js and bun_environment.js

  3. Actor

    No source we cite attributes this activity to an actor.

  4. Infrastructure

    • Public GitHub repos used as exfil dead drops
    • Self-hosted GitHub runners named SHA1HULUD

    Last seen

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
sha256a3894003ad1d293ba96d77881ccd2071446dc3f65f434669b49b3da92421901a
sha25662ee164b9b306250c1172583f138c9614139264f889fa99614903c12755468d0
sha256cbb9bc5a8496243e02f3cc080efbe3e4a1430ba0671f2e43a202bf45b05479cd

Confidence: Moderate

Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.

Sources

Notes

  • Start date varies (21 vs 24 Nov 2025). Secrets leaked here later enabled trust-wallet-extension-2-68-compromise.

Corrections

No corrections.

See the corrections policy. Spotted an error? Tell us.