Which versions of @keyv/encrypt-node are malicious?

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

How do I remediate @keyv/encrypt-node if I installed it?

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

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

Yes — @keyv/encrypt-node is associated with the GHSA-5v34-xm6r-f57w, IN-MAL-2026-014257 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/encrypt-node 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/encrypt-node (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/encrypt-node across your stack and pipelines.

Part of a larger attack: @keyv published 19 malicious packages. See the full campaign →

Malicious package

@keyv/encrypt-nodenpm

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

MAL-2026-12013

Immediate action

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

npm uninstall @keyv/encrypt-node

What this malware does

No static or traced-code signals of installer-side attack were observed in this version of @keyv/encrypt-node. No lifecycle-script fetch-and-execute, no credential or environment scraping, no hardcoded exfiltration endpoints, and no obfuscated payloads were identified 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)

592314a6ca4102bf0da8eaeb88e30814b2f1b6fcefaccd42277ed1d2fd2a2699

9c28175ab56ea558a0634ba48421de59c05f3ebc5e06335162cd2d30a6972495

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/encrypt-node (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/encrypt-node across your stack and pipelines.
If you installed it — respond
@keyv/encrypt-node 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/encrypt-node 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/encrypt-node 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/encrypt-node 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-5v34-xm6r-f57wIN-MAL-2026-014257

References

Credits

Amazon Inspector · finder

Detect & block this

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