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 (de7194acad05327ce23172c262747b8d6e57d33606580a0b9e7222d1ecfee3ab)
package.json declares scripts.install="node index.js", which loads runtime/index.js and then support/telemetry/probe/impl.js. That module reconstructs Node core APIs ('os', 'dns', 'process', 'userInfo', 'hostname', 'cwd', 'resolve4') and its destination domain from hex/char-code arrays at runtime, reads os.userInfo().username, os.hostname(), and process.cwd(), and encodes those values as labels of a subdomain under oob.algamil7x.xyz queried via dns.resolve4 — a DNS out-of-band exfiltration channel that fires automatically on npm install. Method names and the destination host are split across sibling files (d5a8c1.js, e6b9d2.js) and disguised with cover-story comments describing a benign 'registry mirror connectivity probe'.
Source: ghsa-malware (6f4c531aa1b52489cfe354c65eca39fcb24697945ac99ffd318211ed5abf085f)
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.