npx-oob-package

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (6302c47700c024cb727f6139b5cd8703da7c295555525ce9624c12b536f76dde)
npx-oob-package ships bin/cli.js which is also declared as the package main. On both CLI invocation and any require()/import of the package, the module collects local identifiers (whoami / os.userInfo(), os.hostname(), os.platform()) along with the package name and POSTs them via fetch() to a hardcoded Cloudflare Workers endpoint at https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9. The callback destination is not configurable and there is no user consent or opt-out. The package presents as an out-of-band (OOB) beacon consistent with dependency-confusion or pentest-style reconnaissance, causing installer host and user identifiers to leave the machine to an author-controlled endpoint on install-triggered require or CLI use.

## Source: ossf-package-analysis (97f657a8f0fdcb9bebaa6ad7caf2775f059ee15fd9e721d1ca66e5bd239ba42c)
The OpenSSF Package Analysis project identified 'npx-oob-package' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

Compromised versions (1)

• 1.0.2

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.