@bscom/styling (npm) · Malicious Code
Affects @bscom/stylingSource GCVE Database
Malicious package : remove @bscom/styling 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-6605
What to do
Remove @bscom/styling 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 |
|---|---|---|
| npm@bscom/styling | 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 @bscom/styling contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys on the affected system should be rotated from a different, clean machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.