Which versions of @zahlen/checkout are malicious?

The following npm versions of @zahlen/checkout are flagged malicious: 0.2.2. Treat any of these as compromised.

How do I remediate @zahlen/checkout if I installed it?

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

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

Yes — @zahlen/checkout is associated with the GHSA-vj9r-9wwp-6cfp, IN-MAL-2026-016003 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 @zahlen/checkout 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 @zahlen/checkout (version 0.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zahlen/checkout across your stack and pipelines.

Malicious package

@zahlen/checkoutnpm

@zahlen/checkout is a confirmed malicious npm package (MAL-2026-13391) that steals credentials and exfiltrates sensitive data (malicious version 0.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zahlen/checkout (npm)

MAL-2026-13391

Immediate action

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

npm uninstall @zahlen/checkout

What this malware does

No a static rule or traced code paths flagged malicious behavior in this package. No lifecycle hooks fetching or executing remote content, no credential or environment scraping, no hardcoded exfiltration endpoints, no silent-relay of caller data, and no persistence mechanisms 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

0.2.2

Indicators of compromise (SHA-256)

608af2e8bd10840c8019a74eef4f73478711e74c777f452ee03097500fc68222

4d1a20d08b428711d9b8c349d981cf4997f086b8cbd8dce407ef26e02706f33e

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 @zahlen/checkout (version 0.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zahlen/checkout across your stack and pipelines.
If you installed it — respond
@zahlen/checkout 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 @zahlen/checkout 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 @zahlen/checkout 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. @zahlen/checkout on npm has been identified as a malicious package (version 0.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vj9r-9wwp-6cfpIN-MAL-2026-016003

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zahlen/checkout-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