create-cf-token (npm) · Malicious Code
Affects create-cf-tokenSource GCVE Database
Malicious package : remove create-cf-token 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-5240
What to do
Remove create-cf-token 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 |
|---|---|---|
| npmcreate-cf-token | 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 create-cf-token versions 1.1.2 and 1.1.3 contains malicious code or depends on a package with malicious code. This malware, known as Miasma, is a self-propagating worm that spreads by abusing binding.gyp files to execute code during package installation, bypassing typical security inspections. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services and propagates by compromising other packages or injecting backdoors into 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/create-cf-token/v/1.1.2 (opens in a new tab)
- npmjs.com/package/create-cf-token/v/1.1.3 (opens in a new tab)
- github.com/advisories/GHSA-cf4c-f3hr-3wh4 (opens in a new tab)
- npmjs.com/package/create-cf-token/v/1.1.4 (opens in a new tab)