signalledger-diagnostics (npm) · Malicious Code
Affects signalledger-diagnosticsSource GCVE Database
Malicious package : remove signalledger-diagnostics 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-18076
What to do
Remove signalledger-diagnostics 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-diagnostics | 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 signalledger-diagnostics version 2.0.6 is identified as part of a malicious campaign involving fake job interview lures. The package is a Tailwind CSS plugin that depends on a private scoped package requiring an npm token, which delivers the actual malicious payload when the plugin is loaded during development. The publicly available tarball does not contain install scripts or network code, and no direct malicious behavior was observed in the shipped files. Multiple similar packages were published under various accounts over a period of months.
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-diagnostics/v/2.0.6 (opens in a new tab)