process-status-widget
This report shows the evidence for process-status-widget@99.9.1, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10581 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
Source inspection finds an inert package with no direct attack behavior. The direct remote dependency remains an unresolved supply-chain risk, warranting a warning rather than a block.
Independent scan evidence
public snapshot- `package.json` pins dependency `ltidisafe` to a remote Google Cloud Storage tarball.
- The tarball dependency is fetched during npm dependency installation and its contents are not present for source review.
- `package.json` has no preinstall, install, or postinstall lifecycle hooks.
- `index.js` only exports an empty object; no import-time behavior.
- No package source uses network, shell execution, file access, or credential collection.
Source & flagged code
1 flagged · loading sourcePackage manifest contains a dependency pinned to a remote tarball URL.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to process-status-widget@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing process-status-widget@99.9.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.