Which versions of @zahlen/checkout-react are malicious?

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

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

@zahlen/checkout-react establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @zahlen/checkout-react — how do I know if it already compromised me?

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

Yes — @zahlen/checkout-react is associated with the IN-MAL-2026-014662, GHSA-x74p-x7r9-958g 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-react 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-react (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zahlen/checkout-react across your stack and pipelines.

Malicious package

@zahlen/checkout-reactnpm

@zahlen/checkout-react is a confirmed malicious npm package (MAL-2026-12333) that opens a backdoor for remote access (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zahlen/checkout-react (npm)

MAL-2026-12333

Immediate action

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

npm uninstall @zahlen/checkout-react

What this malware does

The package's main module contains a top-level block that runs on every require/import. It uses unicode-escape obfuscation (\uXXXX) to hide imports of Node built-ins including child_process (spawn), http, https, zlib, and url. The prelude resolves a command-and-control host by querying Ethereum blockchain state via https://eth.blockscout.com/api keyed off contract address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a (with a public ETH RPC fallback list), then polls http://<resolved-host>:443/0x/ls and /0x/cls on that host and feeds the retrieved tasks into child_process.spawn, giving a remote operator arbitrary command execution on any developer machine or CI runner that installs or imports the package. The prelude also stashes global.r=require and global.m=module so C2-delivered payloads can load additional Node built-ins without repeating the unicode-escaped require dance. The React checkout code shipped below the prelude is cover; the on-chain C2 resolution is a rotation mechanism that lets the operator move infrastructure without republishing the package.

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.1.1

Indicators of compromise (SHA-256)

097440ff1155e4d840568cf0fc8502c00d43249340f0f301167a859fd34c9fe8

e8ea4ffb2df60ad2438699518b35cd7acdf501aa0de47a10a479f4a523079b7f

dc913167f0dbadc44b40ab97ad7b3f47dae3dd36b4b13acb0b910490635d8b9b

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zahlen/checkout-react (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zahlen/checkout-react across your stack and pipelines.
If you installed it — respond
@zahlen/checkout-react establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @zahlen/checkout-react 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-react 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-react on npm has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014662GHSA-x74p-x7r9-958g

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zahlen/checkout-react-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database