Which versions of @keyv/mongo are malicious?

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

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

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

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

Yes — @keyv/mongo is associated with the GHSA-h8h5-wqhj-grm7, IN-MAL-2026-014269 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/mongo 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/mongo (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/mongo across your stack and pipelines.

Malicious package

@keyv/mongonpm

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

MAL-2026-12017

Immediate action

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

npm uninstall @keyv/mongo

What this malware does

@keyv/mongo is the MongoDB storage adapter for the keyv key-value library. No a static rule matched and no behavioral findings were produced against this version's contents. No lifecycle scripts fetching or executing remote code, no credential or filesystem reads targeting installer secrets, no hardcoded non-first-party network destinations, and no obfuscated payloads were observed.

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)

5a31cfa00db5609eb8dea14b12e50bf7bf4354eba2990b524805c7da863bc97a

b54da8d83c19dc23fe163d7e333f4529faa01d322fe272066da4964fcf604469

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/mongo (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/mongo across your stack and pipelines.
If you installed it — respond
@keyv/mongo 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/mongo 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/mongo 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/mongo 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-h8h5-wqhj-grm7IN-MAL-2026-014269

References

Credits

Amazon Inspector · finder

Detect & block this

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