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

mzek-scanproc

v1.0.0

Published

linux: scan /proc for hidden processes

Readme

mzek-scanproc

This is a POC in scanning /proc for hidden processes on linux systems without brute forcing the PID address space.. I was checking out this article and I created a process hiding kernel module that hides a node js process called hidden.js.

I realised that fs.readdirSync found the hidden PID that was invisible to ps aux or lsof -ni during my experimentation. This is way faster than iterating through the PID range but I'm not sure if its going to catch every type of hidden processes or how it works yet.

I took inspiration from this tool from sandfly security that iterates the PID range looking for processes that are hidden.

install

npm i mzek-scanproc -g

create a kernel module and load it (see /notes).

$ cd ./notes
$ make
$ sudo mv libprocesshider.so /usr/local/lib/
$ echo /usr/local/lib/libprocesshider.so >> /etc/ld.so.preload
$ node hidden.js

extracted output showing the hidden PID

{
 '/usr/bin/node',
    '/home/monz/Desktop/experiments/scanproc/hidden.js'
  ],
  execArgv: [],
  pid: 19435,
  ppid: 5363,
  execPath: '/usr/bin/node',
  debugPort: 9229,
  argv0: 'node',
  _preload_modules: [],
}

check for hidden PIDs

$ scanproc
<mzek-scanproc>
<mzek-scanproc>
found hidden PIDs  [ 19435 ]

investigation

  • does this work with any time of hidden process or just node?
  • how does node's fs module detect the PID that is hidden from ps?

Leave an issue if you know how this works.

resources