Which versions of cb-wallet-http are malicious?

The following npm versions of cb-wallet-http are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate cb-wallet-http if I installed it?

cb-wallet-http 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 cb-wallet-http — how do I know if it already compromised me?

If cb-wallet-http 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 cb-wallet-http part of a known attack campaign?

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

Malicious package

cb-wallet-httpnpm

Malicious code in cb-wallet-http (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4507

Immediate action

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

npm uninstall cb-wallet-http

What this malware does

Package name mimics Coinbase's internal cb-wallet-* namespace to capture dependency-confusion resolutions. On npm install (postinstall.js) and on require('cb-wallet-http') (index.js), the package issues an HTTPS GET to the hardcoded endpoint https://icy-cell-fb53.gh0stfqce25.workers.dev/poc, transmitting the package name and Node.js runtime version to a third-party Cloudflare Workers domain registered under a personal handle (gh0stfqce25.workers.dev) unrelated to Coinbase. The package's own description self-identifies as a 'RESERVED PLACEHOLDER — coordinated security-research namespace claim' with the repository github.com/gh0stfqce/npm-namespace-claims. Regardless of the author's stated research intent, any organization that installs this package via misconfigured registry resolution leaks host/build-topology identifiers to the operator of the worker without consent, fingerprinting which builds are vulnerable to dependency confusion against Coinbase's namespace.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

965e8e6b8edf601543514ba8f6cfa8a0393f8acfddaa3cc89b472642556e6020

e8d704c0a6a48da0e2fef8eddcd1f98e7d380c3e19f22753f3df51d9893f60ce

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

Campaign

IN-MAL-2026-003586IN-MAL-2026-003585

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cb-wallet-http-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