NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

npm-sandbox-ping-r9t2npm

Advisory published Updated

npm-sandbox-ping-r9t2 is a confirmed malicious npm package (MAL-2026-5986) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in npm-sandbox-ping-r9t2 (npm)

MAL-2026-5986
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall npm-sandbox-ping-r9t2

What this malware does

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

335649d395a44d7de1bc6343dbce1f0459414ef92ab149413a86b47e28f3c7c3
ad2de245b09aeb12d92a3e2edbe8ca8ecf88e4211ff95cc51355810b57b70aa4

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for npm-sandbox-ping-r9t2 (version 1.0.0).

  2. If you installed it — respond

    npm-sandbox-ping-r9t2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If npm-sandbox-ping-r9t2 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. npm-sandbox-ping-r9t2 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006898GHSA-p3jc-qrj7-hj68

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks npm-sandbox-ping-r9t2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

npm-sandbox-ping-r9t2 (npm) malicious package — MAL-2026-5986 | O3 Security