creditcard.js (npm) · Malicious Code
Affects creditcard.jsSource GCVE Database
Malicious package : remove creditcard.js and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 15:56 UTC
Malicious package
Published to npm · OSV MAL-2026-5242
What to do
Remove creditcard.js from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmcreditcard.js | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package creditcard.js versions 2.1.8 and 3.0.60 contain malicious code associated with the Miasma malware. This malware is a self-propagating worm that spreads by abusing weaponized binding.gyp files during package installation. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or committing backdoor files to GitHub repositories.
References
- endorlabs.com/learn/malicious-payload-in-ai-sdk-ollama-npm-package (opens in a new tab)
- stepsecurity.io/blog/binding-gyp-npm-supply-chain-attack-spreads-like-worm (opens in a new tab)
- npmjs.com/package/creditcard.js/v/3.0.60 (opens in a new tab)
- npmjs.com/package/creditcard.js/v/2.1.8 (opens in a new tab)
- github.com/advisories/GHSA-6v78-xg39-f56q (opens in a new tab)