# MAL-2026-15597: Malicious code in npx-oob-package (npm)


- **Type:** Malicious package
- **Package:** `npx-oob-package` (npm)
- **Published:** 29 Aug 2026
- **Also known as:** GHSA-95gx-59fv-gfg6

## What is MAL-2026-15597?

MAL-2026-15597 is a malicious package in npx-oob-package, published on 29 Aug 2026. 

### Official description

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.

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.

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.

## What should I do about MAL-2026-15597?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-15597 is a malicious package: npx-oob-package (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-15597/ (Markdown: https://insights.sbomify.com/MAL-2026-15597/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-15597

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-15597/
Summaries are generated and may contain mistakes; the official description above is the record.