Which versions of signalledger-bridge are malicious?

The following npm versions of signalledger-bridge are flagged malicious: 2.0.6. Treat any of these as compromised.

How do I remediate signalledger-bridge if I installed it?

signalledger-bridge is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed signalledger-bridge — how do I know if it already compromised me?

If signalledger-bridge was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find signalledger-bridge across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for signalledger-bridge (version 2.0.6).

Malicious package

signalledger-bridgenpm

Advisory published Oct 19, 2026Updated Oct 20, 2026

signalledger-bridge is a confirmed malicious npm package (MAL-2026-18075) that steals credentials and exfiltrates sensitive data (malicious version 2.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in signalledger-bridge (npm)

MAL-2026-18075

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall signalledger-bridge

What this malware does

signalledger-bridge (2.0.6) is a Tailwind CSS plugin from the fake job interview campaign behind MAL-2026-17665 and MAL-2026-17666: the same Animate.css integration template, README and description, published by scott-rogers on 2026-09-28. src/motion.js:5 requires the private scoped package @jasperquinn/postcss-motion-helpers, which is not readable on the public registry and resolves only with the npm token committed in the lure repository's web/.npmrc, so the code it delivers runs when tailwind.config.js loads the plugin and the dev server starts. The published tarball contains no install scripts and no network code; the payload lives in the private dependency, which was not retrieved. Twenty-six such packages under seventeen accounts were published between 2026-07-28 and 2026-10-09.

Malicious versions

1 flagged

2.0.6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for signalledger-bridge (version 2.0.6).
If you installed it — respond
signalledger-bridge is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If signalledger-bridge was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. signalledger-bridge on npm has been identified as a malicious package (version 2.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

pkgwarden · finder

Detect & block this

O3 blocks signalledger-bridge-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database