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

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

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

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

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

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

Malicious package

@zahlen/checkout-angularnpm

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

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

MAL-2026-12332

Immediate action

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

npm uninstall @zahlen/checkout-angular

What this malware does

The package's fesm2022 ESM entry (declared as module in package.json and executed on import of the library) ends with a trailing eval(atob('...')) payload that, once decoded, requires child_process, http, https, and zlib via \uXXXX-escaped identifier strings to hide the imports from static scanners. The loader queries an Ethereum contract at 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a through https://eth.blockscout.com/api (with public RPC fallbacks 1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io) to read attacker-controlled host/port values from contract storage, then reaches those hosts over HTTP at paths http://${host}:443/0x/cls and http://${host}:443/0x/ls and passes the returned bytes to child_process.spawn. This is an EtherHiding remote-code-execution channel: consuming the library in any Node context that evaluates the ESM (SSR, build tooling, dev servers, tests) triggers on-chain-directed download and execution of arbitrary attacker code. The loader is unrelated to the package's advertised checkout functionality, is appended after the legitimate export { ZahlenModule,... } bundle, and is base64+unicode-obfuscated — hallmarks of an injected supply-chain payload rather than package feature code.

Malicious versions

1 flagged

0.1.4

Indicators of compromise (SHA-256)

45fa3b05e748470cdc08e19b2e86efb8a34c85f155e5972c1b0c0598c150a0bd

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

Campaign

IN-MAL-2026-014769

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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