poly-kelly (npm) · Malicious Code
Affects poly-kellySource GCVE Database
Malicious package : remove poly-kelly and rotate any secrets on hosts that installed it.
Data as of 30 Jul 2026, 09:20 UTC
Malicious package
Published to npm · OSV MAL-2026-6584
What to do
Remove poly-kelly 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 |
|---|---|---|
| npmpoly-kelly | 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 'poly-kelly' version 3.5.3 contains malicious code that executes during installation. Its postinstall script fetches a JSON configuration from a remote URL, downloads and extracts a tarball containing additional code, installs dependencies, and executes a function from the downloaded code. This process lacks integrity checks, allowing arbitrary JavaScript to run on the installer's machine. The package metadata is suspicious, lacking author and repository information, and uses the homepage field as a command-and-control configuration endpoint. Any system with this package installed should be considered fully compromised.
References
- npmjs.com/package/poly-kelly/v/3.5.3 (opens in a new tab)
- npmjs.com/package/poly-kelly/v/3.3.0 (opens in a new tab)
- npmjs.com/package/poly-kelly/v/3.1.0 (opens in a new tab)
- npmjs.com/package/poly-kelly/v/3.2.0 (opens in a new tab)
- npmjs.com/package/poly-kelly/v/3.5.2 (opens in a new tab)
- github.com/advisories/GHSA-c37j-v3j2-6gf8 (opens in a new tab)