@sectest429/hello-npm-worldnpm

The package advertises a single function module.exports = function hello(name) but ships a preinstall.js lifecycle script that runs automatically on npm install and performs reconnaissance unrelated to the advertised functionality. The script collects OS username, hostname, platform/arch, and the full running process list (ps -eo comm= on POSIX, tasklist /fo csv /nh on Windows), and issues an HTTP PUT to the AWS EC2 link-local IMDSv2 token endpoint at 169.254.169.254/latest/api/token followed by a fetch of /latest/meta-data/instance-id. Results are written to ./exfil.log in the installer's working directory. The file's own header comment self-describes as a 'SECURITY DEMO payload' proving that a trojanized package gets code execution at install time. Even though the current version writes locally rather than transmitting, the recon chain (process enumeration + cloud-instance fingerprinting) has no relationship to a hello-world library, runs without consent on every install, and pollutes the consumer's CWD with an artifact.

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.