NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @keyv published 19 malicious packages. See the full campaign →
Malicious package

@keyv/redisnpm

Advisory published Updated

@keyv/redis is a confirmed malicious npm package (MAL-2026-12020) 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/redis (npm)

MAL-2026-12020
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @keyv/redis

What this malware does

Analysis of @keyv/[email protected] produced no a static rule matches and no traced behavioral findings. The package is a Redis storage adapter for the keyv key-value abstraction and does not exhibit lifecycle-script execution, credential access, network exfiltration, or other installer-directed behavior in the scanned files.

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)

85552d13ea23a2ba81a6e8020f7b5b6466f02b92f153be4874c1e975ea11a254
8c6bb14bdfcd4aae57a41c9e6e04cd5f612b12e0f45fbcb57510ccb44b095e77

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @keyv/redis (version 6.0.0).

  2. If you installed it — respond

    @keyv/redis 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.

  3. Did it already run?

    If @keyv/redis 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. @keyv/redis 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-q99r-cjmf-3xrfIN-MAL-2026-014265

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@keyv/redis (npm) malicious package — MAL-2026-12020 | O3 Security