signalledger-bridge (npm) · Malicious Code
Affects signalledger-bridgeSource GCVE Database
Malicious package : remove signalledger-bridge and rotate any secrets on hosts that installed it.
Data as of 29 Oct 2026, 18:11 UTC
Malicious package
Published to npm · OSV MAL-2026-18075
What to do
Remove signalledger-bridge 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 |
|---|---|---|
| npmsignalledger-bridge | 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 signalledger-bridge npm package version 2.0.6 is associated with a malicious campaign involving fake job interview lures. The package itself contains no install scripts or network code, but it depends on a private scoped package that delivers the malicious payload when the plugin is loaded in Tailwind CSS. The private dependency is not publicly accessible and requires an npm token, which was exposed in the lure repository. Multiple related malicious packages were published over several months under different accounts.
References
- osv.dev/vulnerability/MAL-2026-17665 (opens in a new tab)
- osv.dev/vulnerability/MAL-2026-17666 (opens in a new tab)
- osv.dev/vulnerability/MAL-2026-17667 (opens in a new tab)
- pkgwarden.com/incidents/fake-interview-tailwind-plugins-npm-october-2026/ (opens in a new tab)
- npmjs.com/package/signalledger-bridge/v/2.0.6 (opens in a new tab)