Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/prashanthnataraj/mini-shai-hulud-detector
Vulnerability ScannersForensicsMalware AnalysisThreat IntelligenceSupply Chain SecurityIncident Response
GitHubprashanthnataraj/mini-shai-hulud-detector

mini-shai-hulud-detector

One-command scanner for the Mini Shai-Hulud npm supply-chain worm (CVE-2026-45321). Detect before rotating tokens.

View Repository
43 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Mini Shai-Hulud Detector

One-command scanner for the Mini Shai-Hulud npm supply-chain attack (CVE-2026-45321, CVSS 9.6).

Critical: detect before rotating tokens

The worm installs a persistence daemon (gh-token-monitor) that runs rm -rf ~ if it detects credential revocation. Do not rotate your GitHub PAT or npm token until you have confirmed the daemon is gone. Detect → remove the daemon → then rotate.

Usage

root@kitploit:~
curl -fsSL https://raw.githubusercontent.com/prashanthnataraj/mini-shai-hulud-detector/main/shai-hulud-detector.sh | bash

Or download and inspect first (recommended for any script you pipe to a shell):

root@kitploit:~
curl -fsSL https://raw.githubusercontent.com/prashanthnataraj/mini-shai-hulud-detector/main/shai-hulud-detector.sh -o shai-hulud-detector.sh
# Read it. Then:
bash shai-hulud-detector.sh

What it checks

StepCheck
1@tanstack/setup phantom package in package-lock.json
2Known malicious payload files (router_init.js, tanstack_runner.js)
3Payload SHA-256 hashes against a known-bad list
4gh-token-monitor persistence daemon (LaunchAgent / systemd / pgrep)
5Unexpected PreToolUse / PostToolUse hooks in ~/.claude/settings.json
6pull_request_target triggers and unpinned action refs in .github/workflows

Exit codes

CodeVerdict
0CLEAN — no indicators found
1SUSPICIOUS — manual review required
2INFECTED — follow the remediation order exactly (see the script output)

A missing package-lock.json returns SUSPICIOUS by design — run the scan after npm install.

Remediation order if INFECTED

  1. Disconnect from the network immediately.
  2. Do NOT run npm install, npm uninstall, or git push.
  3. Remove the daemon first — the script output tells you the exact path.
  4. Remove the payload files.
  5. Only then: reconnect and rotate credentials (GitHub PAT first).
  6. Reinstall: rm -rf node_modules && npm install --ignore-scripts.

Hardening (worth doing regardless of the scan result)

Add to .npmrc:

root@kitploit:~
ignore-scripts=true
minimum-release-age=4320

Pin all GitHub Actions to a full commit SHA, not a version tag.

About

Written after the Lume AI team encountered a live CVE-2026-45321 attack in May 2026. The script is read-only — no network calls after download, no writes to disk. Review the source before running it.

License

MIT — see LICENSE.

Download Tool