Malicious code in @zahlen/checkout-angular (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (45fa3b05e748470cdc08e19b2e86efb8a34c85f155e5972c1b0c0598c150a0bd) 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. ## Source: ghsa-malware (a3a38f34dcb95f0e345748ebb65454acd70b9fef5253e93f63e74c87b5278f23) 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.
AI Analysis
Technical Summary
The @zahlen/checkout-angular npm package version 0.1.4 includes a supply-chain injected payload appended after the legitimate module exports. The payload is obfuscated using base64 and unicode escapes and uses eval to execute. It dynamically requires Node.js modules such as child_process, http, https, and zlib using escaped identifiers to avoid detection by static scanners. The malicious code queries an Ethereum contract at address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a via the Blockscout API and several public RPC endpoints to retrieve attacker-controlled host and port values. It then connects to these hosts over HTTP on port 443 and downloads data from specific paths, which it executes using child_process.spawn. This behavior constitutes a remote code execution channel controlled via on-chain data, representing a severe supply-chain compromise risk.
Potential Impact
Any Node.js environment that imports the ESM module of @zahlen/checkout-angular version 0.1.4 will execute attacker-controlled code, leading to remote code execution. This can result in full system compromise, data theft, or further malware deployment. The attack leverages blockchain-based command and control, making detection and mitigation more complex. This affects build tooling, server-side rendering, development servers, and tests that import the package.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately stop using version 0.1.4 of @zahlen/checkout-angular. Audit dependencies for this package and remove or replace it. Monitor for updates from the package maintainers or npm advisories for any official fixes. Until a fix is available, avoid importing this package in any Node.js context.
Malicious code in @zahlen/checkout-angular (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (45fa3b05e748470cdc08e19b2e86efb8a34c85f155e5972c1b0c0598c150a0bd) 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. ## Source: ghsa-malware (a3a38f34dcb95f0e345748ebb65454acd70b9fef5253e93f63e74c87b5278f23) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @zahlen/checkout-angular npm package version 0.1.4 includes a supply-chain injected payload appended after the legitimate module exports. The payload is obfuscated using base64 and unicode escapes and uses eval to execute. It dynamically requires Node.js modules such as child_process, http, https, and zlib using escaped identifiers to avoid detection by static scanners. The malicious code queries an Ethereum contract at address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a via the Blockscout API and several public RPC endpoints to retrieve attacker-controlled host and port values. It then connects to these hosts over HTTP on port 443 and downloads data from specific paths, which it executes using child_process.spawn. This behavior constitutes a remote code execution channel controlled via on-chain data, representing a severe supply-chain compromise risk.
Potential Impact
Any Node.js environment that imports the ESM module of @zahlen/checkout-angular version 0.1.4 will execute attacker-controlled code, leading to remote code execution. This can result in full system compromise, data theft, or further malware deployment. The attack leverages blockchain-based command and control, making detection and mitigation more complex. This affects build tooling, server-side rendering, development servers, and tests that import the package.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately stop using version 0.1.4 of @zahlen/checkout-angular. Audit dependencies for this package and remove or replace it. Monitor for updates from the package maintainers or npm advisories for any official fixes. Until a fix is available, avoid importing this package in any Node.js context.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12332
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735745bf8831d539159f4d
Added to database: 08/05/2026, 15:31:17 UTC
Last enriched: 08/05/2026, 17:25:41 UTC
Last updated: 09/07/2026, 22:12:19 UTC
Views: 20
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.