@uh-platform/nadaver2npm
@uh-platform/nadaver2 is a confirmed malicious npm package (MAL-2026-16361) that executes malicious code on install (malicious version 102.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @uh-platform/nadaver2 (npm)
What this malware does
The package's package.json declares a preinstall lifecycle hook that runs node index.js. index.js invokes child_process.exec on a curl command whose URL embeds $(hostname) and $(whoami) as DNS subdomains of nadaver.pa33pg1od9cr4ffnrzec8864jvpmdd12.oastify.com, a Burp Collaborator (OAST) endpoint. On npm install, the installer's hostname and OS username are transmitted to that attacker-controlled collaborator host via DNS and HTTP. The @uh-platform scope and the name shape are consistent with a dependency-confusion probe. There is no legitimate SDK, build, or install functionality in the package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @uh-platform/nadaver2 (version 102.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @uh-platform/nadaver2 across your stack and pipelines.
If you installed it — respond
Remove @uh-platform/nadaver2 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @uh-platform/nadaver2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @uh-platform/nadaver2 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @uh-platform/nadaver2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.