Which versions of @keyv/bigmap are malicious?

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

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

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

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

Yes — @keyv/bigmap is associated with the GHSA-p677-p29q-h534, IN-MAL-2026-014268 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/bigmap 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/bigmap (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/bigmap across your stack and pipelines.

Malicious package

@keyv/bigmapnpm

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

MAL-2026-12007

Immediate action

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

npm uninstall @keyv/bigmap

What this malware does

The package contents did not exhibit any behaviors associated with supply-chain attacks: no install/preinstall/postinstall lifecycle hooks fetching or executing remote content, no reads of installer credential paths (~/.aws, ~/.ssh, ~/.npmrc, browser stores), no environment-variable scraping, no hardcoded network exfiltration endpoints, no obfuscated payloads, and no persistence mechanisms. Behavior is consistent with the package's documented purpose as a 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)

4c0b2769ba453f277c09380e6b3b8b00b561ae11c77125f5a98dfbe86aaf85ea

2a8f8e82f91c41a43a5730b8c4d545e0b2e7b8b43b0945d656f937ce6b4adf79

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/bigmap (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/bigmap across your stack and pipelines.
If you installed it — respond
@keyv/bigmap 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/bigmap 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/bigmap 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/bigmap 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-p677-p29q-h534IN-MAL-2026-014268

References

Credits

Amazon Inspector · finder

Detect & block this

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