Malicious code in crypto-checkout-api (npm)
MAL-2026-12666 · GHSA-cg47-54wp-xjp9
Published · Modified
Dependency scanning
Check whether crypto-checkout-api is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (b15806df14aa955b2d5e08414d4f22ad71a9d1ac823aa7557e8f9d490d78761d)
index.js exports getPlugin() which issues an HTTPS request to a hardcoded bare-IP endpoint at https://46.183.25.232:45000/icons/112 and passes the response field data.credits to new Function('require','module',...,data.credits), executing attacker-controlled JavaScript with require, process, and Buffer injected. The request is framed with cover-story naming (a font-awesome/CDN path fragment and a 'bearrtoken: logo' header) that is unrelated to the actual bare-IP destination and inconsistent with the package's stated 'crypto checkout' purpose. Declared dependencies (@primno/dpapi for Windows DPAPI unwrap, node-machine-id, better-sqlite3) are consistent with a credential/wallet-stealer payload delivered through the loader.
Source: ghsa-malware (36320c265cebe6479c4c4d438a043d4c38fb14b9e02bd8f97130c557b19a2b2c)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes