Which versions of argon2-napi are malicious?

Every published version of argon2-napi on npm is considered malicious. Remove the package entirely.

How do I remediate argon2-napi if I installed it?

argon2-napi 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.

I already installed argon2-napi — how do I know if it already compromised me?

If argon2-napi 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.

How do I find argon2-napi across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for argon2-napi (all published versions).

Malicious package

argon2-napinpm

Advisory published Apr 7, 2026Updated Apr 10, 2026

argon2-napi is a confirmed malicious npm package (MAL-2026-2511) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in argon2-napi (npm)

MAL-2026-2511

Immediate action

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

npm uninstall argon2-napi

What this malware does

Malicious package due to data exfiltration in preinstall script.

The package argon2-napi was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

256afce3626d671d3e6fe9a53923ab5e85da899bd5255e0b975fe5fc22ab417e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for argon2-napi (all published versions).
If you installed it — respond
argon2-napi 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 argon2-napi 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

No. argon2-napi on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

app.safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks argon2-napi-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database