Which versions of @keyv/valkey are malicious?

The following npm versions of @keyv/valkey are flagged malicious: 6.0.0. Treat any of these as compromised.

How do I remediate @keyv/valkey if I installed it?

@keyv/valkey 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 @keyv/valkey — how do I know if it already compromised me?

If @keyv/valkey 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 @keyv/valkey part of a known attack campaign?

Yes — @keyv/valkey is associated with the GHSA-2x7p-3882-mgcg, IN-MAL-2026-014274 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 @keyv/valkey 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 @keyv/valkey (version 6.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @keyv/valkey across your stack and pipelines.

Malicious package

@keyv/valkeynpm

@keyv/valkey is a confirmed malicious npm package (MAL-2026-12025) that steals credentials and exfiltrates sensitive data (malicious version 6.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @keyv/valkey (npm)

MAL-2026-12025

Immediate action

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

npm uninstall @keyv/valkey

What this malware does

The package is a Keyv storage adapter for Valkey. No install-time lifecycle scripts, credential access, network exfiltration, dropper behavior, silent-relay, or backdoor mechanisms were observed in the shipped files. Behavior is consistent with a standard keyv storage adapter.

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.

Malicious versions

1 flagged

6.0.0

Indicators of compromise (SHA-256)

6aab55b50b76a7275c3fadcfe135b930c96e80e78fec7b8232f8aae423f90f80

77c74b9b7cab0e47c6f19a96a7ea44fd6d7c23989e4abdab3e708de9d6084d7f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @keyv/valkey (version 6.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @keyv/valkey across your stack and pipelines.
If you installed it — respond
@keyv/valkey 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 @keyv/valkey 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 @keyv/valkey 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. @keyv/valkey on npm has been identified as a malicious package (version 6.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2x7p-3882-mgcgIN-MAL-2026-014274

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @keyv/valkey-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