Skip to content
OpenAdvisories
Malicious MAL-2026-5986 GHSA-p3jc-qrj7-hj68

npm-sandbox-ping-r9t2

npm package · versions 1.0.0

Reported Jun 17, 2026 · Updated Jun 18, 2026

If this package is installed

Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.

Details

Source: amazon-inspector (335649d395a44d7de1bc6343dbce1f0459414ef92ab149413a86b47e28f3c7c3)
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.

Source: ghsa-malware (ad2de245b09aeb12d92a3e2edbe8ca8ecf88e4211ff95cc51355810b57b70aa4)
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.