Which versions of crypto-checkout-api are malicious?

The following npm versions of crypto-checkout-api are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate crypto-checkout-api if I installed it?

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

If crypto-checkout-api 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 crypto-checkout-api part of a known attack campaign?

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

Malicious package

crypto-checkout-apinpm

crypto-checkout-api is a confirmed malicious npm package (MAL-2026-12666) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in crypto-checkout-api (npm)

MAL-2026-12666

Immediate action

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

npm uninstall crypto-checkout-api

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b15806df14aa955b2d5e08414d4f22ad71a9d1ac823aa7557e8f9d490d78761d

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

Campaign

IN-MAL-2026-014936

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks crypto-checkout-api-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