npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

shai-hulud-scanner

v1.0.0

Published

Pure Node Shai Hulud infestation scanner

Readme

Shai Hulud Scanner

Pure Node.js, read-only scanner for Shai Hulud indicators found in the local reference source. It uses only Node built-ins and does not install dependencies.

Usage

npm run scan
npm run scan:home
node index.js --path /some/project --json
node index.js --full --exclude /known/reference/source
node index.js --home --no-progress

The default scan checks active processes, known persistence and lock locations, and the current directory. --home is the practical broad scan for a developer machine. --full is slower and skips pseudo filesystems. Human scans show a Unicode progress loader on stderr; JSON output stays machine-readable.

What It Checks

  • Active process command lines for known payload and monitor names.
  • Known lock and persistence paths for the user-level token monitor.
  • npm package backdoors that run a local setup loader.
  • repository mutations under .claude, .vscode, and GitHub workflow paths.
  • exact hashes of known loader, hook, workflow, and monitor assets.
  • compound content patterns for secret-exfiltration workflows and Bun loaders.

Exit code 0 means no medium-or-higher findings. Exit code 1 means suspicious or high-confidence indicators were found. The scanner never deletes files or prints token contents.