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 (1d079b30dbb30db1a61acddcd094d2e7e67e7ef466d624e4ad2392edc9d9203e)
On install, package.json runs `postinstall: node run.js`. run.js imports os, fs, http, https, and child_process and at runtime collects host identifiers (os.hostname(), os.platform()) and reads files from the filesystem (fs.existsSync / fs.readFileSync), then issues outbound HTTP/HTTPS requests including POST calls (run.js lines 322, 329) and GET / http.get fetches (lines 38, 190). The postinstall lifecycle hook causes this code to execute automatically on `npm install` without consumer interaction, exposing installer host information and local file contents to attacker-controlled network destinations. The package name (random suffix `-77d4`) and the absence of any documented purpose are consistent with a disposable exfiltration lure rather than a legitimate library.
Source: ghsa-malware (52d1d3e23a5ff1effade9c537dc09744ccceaa12c6cd344a0627d1513be34899)
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.