# MAL-2026-5762: Malicious code in npm-sandbox-research-e9f0 (npm)


- **Type:** Malicious package
- **Package:** `npm-sandbox-research-e9f0` (npm)
- **Published:** 14 Jun 2026
- **Also known as:** GHSA-76w8-rxxx-vjcg

## What is MAL-2026-5762?

MAL-2026-5762 is a malicious package in npm-sandbox-research-e9f0, published on 14 Jun 2026. 

### Official description

Package declares a postinstall hook ("postinstall": "node run.js") that executes automatically on npm install. The tarball ships beacon scripts (beacon13.js, beacon_linux.js) that combine require('child_process'), require('os'), and require('http')/http.request to gather host identifiers (os.hostname(), os.platform()) and transmit them via HTTP POST/GET requests. This is the canonical install-time host-recon and exfiltration shape: lifecycle hook auto-execution, host enumeration via the os module, command execution capability via child_process, and outbound HTTP. Installing this package causes immediate disclosure of host metadata and provides a code-execution surface on the installer's machine.

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.

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

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-5762 is a malicious package: npm-sandbox-research-e9f0 (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-5762/ (Markdown: https://insights.sbomify.com/MAL-2026-5762/index.md)
```

## Sources

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

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