Which versions of nerite-security-audit are malicious?

Every published version of nerite-security-audit on npm is considered malicious. Remove the package entirely.

How do I remediate nerite-security-audit if I installed it?

nerite-security-audit 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 nerite-security-audit — how do I know if it already compromised me?

If nerite-security-audit 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 nerite-security-audit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nerite-security-audit (all published versions).

Malicious package

nerite-security-auditnpm

Advisory published Apr 6, 2026Updated Apr 7, 2026

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

Malicious code in nerite-security-audit (npm)

MAL-2026-2499

Immediate action

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

npm uninstall nerite-security-audit

What this malware does

Collects and exfiltrates sensitive data (env vars, SSH keys, keystores, history) via HTTPS and DNS. Suspicious domain and disabled SSL validation.

The package nerite-security-audit 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)

87776a4e480d244c862e76238cd498aa49bd919403dad6de21a85326d6b451ed

Detection & response playbook

Credential / info stealer

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