kelly-stake (npm) · Malicious Code
Affects kelly-stakeSource GCVE Database
Malicious package : remove kelly-stake and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 15:55 UTC
Malicious package
Published to npm · OSV MAL-2026-6482
What to do
Remove kelly-stake 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 |
|---|---|---|
| npmkelly-stake | 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 kelly-stake npm package versions 3.5.2 through 3.5.6 contain malicious code that executes arbitrary commands on the consumer's machine during installation. The postinstall script downloads and runs unverified remote code from an attacker-controlled domain, enabling remote code execution without user awareness. This behavior allows the attacker to rotate payloads dynamically without republishing the package. The installation process suppresses errors to avoid detection, ensuring the malicious code runs on every installation.
References
- npmjs.com/package/kelly-stake/v/3.5.6 (opens in a new tab)
- npmjs.com/package/kelly-stake/v/3.5.2 (opens in a new tab)
- npmjs.com/package/kelly-stake/v/3.5.4 (opens in a new tab)
- npmjs.com/package/kelly-stake/v/3.5.5 (opens in a new tab)
- npmjs.com/package/kelly-stake/v/3.5.3 (opens in a new tab)
- github.com/advisories/GHSA-9x8c-c54x-vgrv (opens in a new tab)
- npmjs.com/package/kelly-stake/v/4.1.0 (opens in a new tab)
- npmjs.com/package/kelly-stake/v/3.3.0 (opens in a new tab)
- npmjs.com/package/kelly-stake/v/3.2.0 (opens in a new tab)
- npmjs.com/package/kelly-stake/v/3.1.0 (opens in a new tab)