Malicious Code Vulnerability in @uh-platform/nadaver: Hostname Leakage via Preinstall Script
Summary
MAL-2026-16360: Malicious code in @uh-platform/nadaver (npm). Affects @uh-platform/nadaver versions 102.0.0. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @uh-platform/nadaver package is an npm library that is likely intended for use in various JavaScript applications. However, it has been found to contain malicious code that executes during the installation process. This vulnerability is particularly concerning as it can expose sensitive information, such as the hostname of the machine where the package is installed, to an attacker-controlled server.
Vulnerability Detail
The vulnerability originates from the package's preinstall script, which executes 'node index.js'. This script uses 'curl' to send a request to a URL that includes the installer's hostname as a subdomain of an attacker-controlled domain. This means that every time the package is installed, the hostname is leaked without any user interaction, potentially allowing attackers to track installations and target specific environments. The malicious behavior is indicative of a dependency-confusion attack, where the package is designed to exploit internal build systems that may resolve the package against the public npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @uh-platform/nadaverIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can avoid using the @uh-platform/nadaver package altogether. If it is necessary to use it, consider isolating the installation in a controlled environment where the hostname leakage will not pose a risk.
Conclusion
The @uh-platform/nadaver package contains a serious vulnerability that exposes the hostname of the installer to an attacker-controlled server. It is crucial to remove this package and monitor for updates. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.
See every vulnerability recorded for @uh-platform/nadaver →
FAQ
The vulnerability involves malicious code that leaks the hostname of the machine during installation, potentially exposing sensitive information to attackers.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can identify if your application is affected.
If you have installed the @uh-platform/nadaver package, it is advisable to remove it immediately and check for any updates or patches from the package maintainers.
To prevent similar vulnerabilities, always review package dependencies, use trusted sources, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
