npx-oob-package
Minimal npx package that POSTs package name and whoami to an OOB callback
This report shows the evidence for npx-oob-package@1.0.2. 2 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package's implemented behavior is an external transfer of local identity and host data to an unrelated hard-coded endpoint. Explicit CLI invocation does not make this covert fingerprint exfiltration package-aligned.
Decision evidence
public snapshot- The CLI collects the current user name, host name, and platform, then posts them to an external callback.
- The callback URL is hard-coded and network failures are silently suppressed.
- There are no npm lifecycle hooks or dependencies.
- The code runs only when the package's explicit CLI command is invoked.
Source & flagged code
6 flagged · loading sourceSource collects local host identity data and sends it to an external endpoint.
bin/cli.jsView on unpkg · L2The CLI collects the current user name, host name, and platform, then posts them to an external callback.
bin/cli.jsView on unpkg · L21The CLI collects the current user name, host name, and platform, then posts them to an external callback.
bin/cli.jsView on unpkg · L35Findings
Affected versions and remediation
This report applies to npx-oob-package@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing npx-oob-package@1.0.2. 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.