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 (2558d8bae443d40330d8166eec921f02de17b395b4359a086a0f12792b026422)
On npm install, the package's preinstall lifecycle script collects the installer's OS username, hostname, and current working directory, walks upward through parent directories to read the enclosing project's package.json (name, author, version), hex-encodes the aggregated JSON, splits it into 60-character DNS labels with a sequence prefix, and issues dns.lookup() queries to the hardcoded nameserver da5u87oh92rc72pp1dngqfc6hp8gwshm6.o.jgl.red. The channel uses DNS rather than HTTP, evading HTTP/proxy egress controls, and fires automatically without user interaction. A source comment framing the behavior as bug-bounty or dependency-confusion research does not alter the mechanism: installer-side identity and enclosing-project identifiers are transmitted to a third-party author-controlled destination.