pm2 7.1.1
PkgFire would install this release with a warning.·Checked 13 hours ago·Published 23 October 2026
Why
-
warnSuspicious behaviour
Detects suspicious autostart persistence mechanisms
-
warnSuspicious behaviour
Detects access to sensitive files (credentials, configs, keys)
-
warnSuspicious behaviour
Detects URLs to URL shorteners, file sharing, and suspicious services
-
warnSuspicious behaviour
Detects HTTP/HTTPS URL dependencies in package.json (dependency confusion, untrusted sources)
-
warnSuspicious behaviour
Detects download-and-execute patterns: fetching a remote file then executing it
-
warnSuspicious behaviour
Detects extensive system/network enumeration activities
-
warnSuspicious behaviour
Possible credential in the published package: generic-api-key
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Verified against the registry's key
- Build provenance
- None, and no earlier version had any
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.