npm-sandbox-ping-r9t2
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-p3jc-qrj7-hj68
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in npm-sandbox-ping-r9t2 (npm)
---
_-= Per source details. Do not edit below this line.=-_
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0