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 (c0916c8694f396dfa0947df6e3b3d3966839a6e02d4a4f5b84f698787c446bdc)
On `npm install`, the package's `preinstall` lifecycle hook runs `node index.js`, which collects host identity (`os.hostname()`, `os.userInfo()`, homedir, DNS servers, cwd) and reads the installer's `/etc/passwd` and `/etc/hosts`, then HTTPS POSTs the combined payload to `ltiyq4zyhrs88zgp5lef9hbec5i46uuj.oastify.com` — a Burp Collaborator (OAST) subdomain controlled by the package publisher. The exfiltration fires automatically on default install with no user interaction. Reading `/etc/passwd` enumerates the installer's local user accounts; the OAST destination provides the publisher with arbitrary out-of-band data capture. This is a textbook dependency-confusion / supply-chain exfiltration beacon.
Source: ghsa-malware (745b957a8874cad0ca26286f04294354427e1ea01ba4f815d78d1b7f3ebdd2a8)
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.