Which versions of coinmarketcap-api are malicious?

The following npm versions of coinmarketcap-api are flagged malicious: 3.1.2, 3.1.3. Treat any of these as compromised.

How do I remediate coinmarketcap-api if I installed it?

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

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

Yes — coinmarketcap-api is associated with the GHSA-3f5p-9hr6-r692 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 coinmarketcap-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 coinmarketcap-api (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging coinmarketcap-api across your stack and pipelines.

Malicious package

coinmarketcap-apinpm

Malicious code in coinmarketcap-api (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190948

Immediate action

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

npm uninstall coinmarketcap-api

What this malware does

The package coinmarketcap-api was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

3.1.23.1.3

Indicators of compromise (SHA-256)

e170f782297c7810953f41d5a4be316d559531427ae8d82691f71c69080313fa

1cf4ed85361338b02dab2cd93a7a4b750f9831838300ce645886aa8e5ef0fb48

befab68e99456bf5a0d0da457e3acc4b6fc2c0c8368027a78f2b59c540abe1b7

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

Campaign

GHSA-3f5p-9hr6-r692

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks coinmarketcap-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