@asdfaskdjfksadhfkasf/nadaver2npm
Advisory published Updated
@asdfaskdjfksadhfkasf/nadaver2 is a confirmed malicious npm package (MAL-2026-16357) that steals credentials and exfiltrates sensitive data (malicious version 102.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @asdfaskdjfksadhfkasf/nadaver2 (npm)
What this malware does
The package declares a preinstall lifecycle script that executes index.js on npm install. index.js uses child_process.exec to run a curl command whose URL embeds $(hostname) and $(whoami) as subdomains of sgc6vj7rjciuailqx2kfebc7pyvpjk79.oastify.com, a Burp Collaborator (OAST) host. On install, the installer's hostname and username are transmitted to that attacker-controlled destination via DNS resolution and HTTP. The package name is a random alphanumeric scope with no legitimate functionality; the sole observable behavior is host reconnaissance exfiltration at install time. This is the canonical dependency-confusion / OAST recon payload shape.
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.
The OpenSSF Package Analysis project identified '@asdfaskdjfksadhfkasf/nadaver2' @ 102.0.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @asdfaskdjfksadhfkasf/nadaver2 (version 102.0.0).
If you installed it — respond
@asdfaskdjfksadhfkasf/nadaver2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @asdfaskdjfksadhfkasf/nadaver2 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @asdfaskdjfksadhfkasf/nadaver2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.