radio-player-theme (npm) · Malicious Code
Affects radio-player-themeSource GCVE Database
Malicious package : remove radio-player-theme and rotate any secrets on hosts that installed it.
Data as of 8 Oct 2026, 07:50 UTC
Malicious package
Published to npm · OSV MAL-2026-16347
What to do
Remove radio-player-theme 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 |
|---|---|---|
| npmradio-player-theme | 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 'radio-player-theme' version 6.0.0 contains a malicious payload in its 'payload.js' file that, when loaded in a browser, reads the origin and a specific XSRF cookie from the victim's environment and exfiltrates this data to an external domain under oastify.com. The package does not execute this code during installation but only when the JavaScript is loaded in a browser context, enabling data collection through a CSP bypass proof-of-concept. The package has no legitimate functionality beyond this data-exfiltration behavior.
References
- npmjs.com/package/radio-player-theme/v/6.0.0 (opens in a new tab)
- github.com/advisories/GHSA-pp2v-g64w-gm6f (opens in a new tab)
- npmjs.com/package/radio-player-theme/v/2.0.0 (opens in a new tab)
- npmjs.com/package/radio-player-theme/v/3.0.0 (opens in a new tab)
- npmjs.com/package/radio-player-theme/v/5.0.0 (opens in a new tab)
- npmjs.com/package/radio-player-theme/v/4.0.0 (opens in a new tab)
- npmjs.com/package/radio-player-theme/v/0.0.0-stage (opens in a new tab)
- npmjs.com/package/radio-player-theme/v/1.0.0 (opens in a new tab)