Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in npx-oob-package (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-15597

Published

--- _-= 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: ghsa-malware (91892d4829cba04960ed5556eb31d1430bc85daa91bd6f01283b40faadba9c63) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## 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.

Source published
29 Aug 2026 20:55:31 UTC
Source modified
4 Sep 2026 06:45:09 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 15:04 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current