# MAL-2026-5986: Malicious code in npm-sandbox-ping-r9t2 (npm)


- **Type:** Malicious package
- **Package:** `npm-sandbox-ping-r9t2` (npm)
- **Published:** 17 Jun 2026
- **Also known as:** GHSA-p3jc-qrj7-hj68

## What is MAL-2026-5986?

MAL-2026-5986 is a malicious package in npm-sandbox-ping-r9t2, published on 17 Jun 2026. 

### Official description

package.json declares a postinstall hook ("postinstall": "node run.js") that auto-executes on install. The package ships beacon scripts (beacon14.js, beacon_linux.js) that import child_process and http/os, run shell commands such as whoami, read process.env, process.platform, os.hostname(), os.platform(), and transmit the collected host/identity data via http.request GET/POST to a remote endpoint. The data flow (system enumeration -> outbound HTTP) and the install-time auto-execution together constitute a credential/host-info exfiltration beacon. Installer harm: any machine that runs `npm install npm-sandbox-ping-r9t2` will silently execute these beacons and leak local identity/environment information to a remote endpoint.

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-5986?

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

## Sources

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

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