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 (ced86462ad99b91f0f3e3d344e008ca911a1dccdad5c928cee5da5c651756f1d)
package.json declares scripts.preinstall = 'node index.js'. On install, index.js collects hostname, username, home directory, cwd, local IPv4, public IP (via api.ipify.org, icanhazip.com, ifconfig.me), DNS resolver information, and the consuming project's package.json fields (name, author, repository, homepage), then transmits the payload to the hardcoded callback host da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun. Transport uses HTTPS POST and HTTP POST to /poc/<uuid>, plus a covert DNS channel that hex-encodes the payload and issues chunked dns.resolve() queries embedding data in subdomain labels under the same host, explicitly to bypass egress filtering that blocks outbound HTTP. The package is published at version 999.9.12 and the README states this high version was chosen so npm resolves the public copy over any internal package of the same name — the canonical dependency-confusion attack shape. Any installer whose resolver falls through to the public registry has host identity and internal project metadata beaconed to a third-party callback with no opt-in.