❯ git clone https://github.com/gensecaihq/Shai-Hulud-2.0-Detector.git ▌

Shai-Hulud 2.0 Detector: Detect the Shai-Hulud 2.0 and ChainDrop npm supply-chain attacks in your repositories

View on GitHub153 stars33 forksTypeScript · MIT licence · by Aloke Majumder

On 24 November 2025, the Shai-Hulud 2.0 supply-chain attack compromised hundreds of npm packages; on 4 August 2026 the campaign returned as ChainDrop. The Shai-Hulud 2.0 Detector is a free GitHub Action that checks whether your repositories are affected.

It scans dependencies, lockfiles and CI workflows against a daily-updated database of more than 1,200 compromised packages from both waves, and looks for the attack's malicious install scripts, credential theft, persistence and backdoor runners. Results can go straight to GitHub Code Scanning as SARIF.

What Shai-Hulud 2.0 Detector Does

1,200+ compromised packages

Precise version and semver-range matching against a daily-updated database covering Shai-Hulud 2.0 and ChainDrop.

Malicious install scripts

Detects the attack's lifecycle-hook payloads such as setup_bun.js and bun_environment.js, with SHA-256 hash matching.

CI and runner backdoors

Flags SHA1HULUD self-hosted runners, fake CodeQL workflows, discussion-triggered workflows and secret-dumping patterns.

IDE and agent persistence

Detects ChainDrop hooks planted in .claude/settings.json and .vscode/tasks.json.

Credential-theft traces

Finds TruffleHog activity and exfiltration files such as truffleSecrets.json and actionsSecrets.json.

SARIF for Code Scanning

Outputs SARIF so findings appear in GitHub Code Scanning; also runs locally and in GitLab or Azure pipelines.

Quick Start

# .github/workflows/shai-hulud-check.yml
name: Shai-Hulud 2.0 Security Check
on: [push, pull_request]
jobs:
  security-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: gensecaihq/Shai-Hulud-2.0-Detector@v2
        with:
          fail-on-critical: true

Full setup and configuration are in the README on GitHub.

Who It's For

Any team with JavaScript or TypeScript projects on npm
Security teams responding to the Shai-Hulud and ChainDrop waves
DevSecOps teams adding supply-chain checks to CI
Maintainers who want to confirm their repositories are clean

Shai-Hulud 2.0 Detector: FAQs

❯

What was the Shai-Hulud 2.0 attack?

A large npm supply-chain attack that began on 24 November 2025. Compromised packages ran malicious install scripts that stole credentials with TruffleHog, exfiltrated them to GitHub repositories and spread to other packages. It returned as ChainDrop on 4 August 2026.

❯

How do I check if my project uses compromised npm packages?

Add the Shai-Hulud 2.0 Detector GitHub Action to a workflow. It scans your dependencies and lockfiles against more than 1,200 known compromised packages and checks for the attack's scripts, runners and exfiltration files.

❯

Does it detect the ChainDrop wave too?

Yes. It covers both Shai-Hulud 2.0 (November 2025) and ChainDrop (August 2026), including ChainDrop's IDE and agent persistence hooks and its C2 infrastructure.

❯

Can I run it outside GitHub Actions?

Yes. It can run as a local CLI and in other CI systems such as GitLab CI and Azure Pipelines.

❯

Is it free?

Yes. The detector is open source under the MIT licence and available on the GitHub Marketplace.

Need help putting it into production?

I built and maintain Shai-Hulud 2.0 Detector. If you want help deploying it, building an AI-assisted SOC around it, or training your team, see AI & security consulting and hands-on training, or get in touch.