Which versions of @keyv/compress-lz4 are malicious?

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

How do I remediate @keyv/compress-lz4 if I installed it?

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

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

Yes — @keyv/compress-lz4 is associated with the GHSA-g3gv-3mfc-gffc, IN-MAL-2026-014248 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/compress-lz4 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/compress-lz4 (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/compress-lz4 across your stack and pipelines.

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

Malicious package

@keyv/compress-lz4npm

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

MAL-2026-12011

Immediate action

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

npm uninstall @keyv/compress-lz4

What this malware does

Package is an LZ4 compression adapter for the keyv key-value store. The dist bundles (dist/index.cjs and dist/index.mjs) contain Buffer.from(..., 'base64')/.toString() calls, which is the expected shape for a compression/serialization codec that encodes and decodes binary payloads. No lifecycle scripts fetching remote content, no environment-variable or credential-path reads, no network exfiltration destinations, and no eval/exec of decoded content are present. The pattern-match on Buffer.from + base64 alone does not indicate installer-side harm.

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)

89a8da4b04376d8125fe67c9ca4c749a6d4633764dcbcedc9988c5cd28fd14a3

cd7fac64e01bf267ca0ee1c3234782fd17c24865d3be3e0cbfa26b65fe83c1a3

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/compress-lz4 (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/compress-lz4 across your stack and pipelines.
If you installed it — respond
@keyv/compress-lz4 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/compress-lz4 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/compress-lz4 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/compress-lz4 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-g3gv-3mfc-gffcIN-MAL-2026-014248

References

Credits

Amazon Inspector · finder

Detect & block this

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