Which versions of routerbase-mcp are malicious?

The following npm versions of routerbase-mcp are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate routerbase-mcp if I installed it?

routerbase-mcp 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 routerbase-mcp — how do I know if it already compromised me?

If routerbase-mcp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is routerbase-mcp part of a known attack campaign?

Yes — routerbase-mcp is associated with the GHSA-rxc6-q384-2wrx, IN-MAL-2026-012908 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find routerbase-mcp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for routerbase-mcp (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging routerbase-mcp across your stack and pipelines.

Malicious package

routerbase-mcpnpm

routerbase-mcp is a confirmed malicious npm package (MAL-2026-11480) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in routerbase-mcp (npm)

MAL-2026-11480

Immediate action

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

npm uninstall routerbase-mcp

What this malware does

The package published as 'routerbase-mcp' declares a bin named 'install-email-research' and ships lib/report.js which collects the installer's email (via 'gh api user/emails', 'git config user.email', and reads of ~/.gitconfig), OS username, and hostname, then POSTs them via https.request to a hardcoded Zapier webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. The postinstall path is non-interactive and only transmits when a prior stored consent decision exists; a CLI prompt requests y/N consent on first interactive run and honors 'no'. No credentials, SSH keys, ~/.aws, ~/.npmrc, or bulk environment variables are read. The package name and description do not disclose this data-collection behavior, the destination is an author-controlled Zapier endpoint rather than infrastructure the installer configures, and the collected fields are developer-identity PII with no credential-grade value.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5bcc3239685adaf9098cfcf2a9f30c0018357be5ad058caf2046534c516bc3a8

1f468779704fb38dd80ed26eabb01f4afdfef486ebb645d99fc07c36dcb479cf

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for routerbase-mcp (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging routerbase-mcp across your stack and pipelines.
If you installed it — respond
routerbase-mcp 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 routerbase-mcp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks routerbase-mcp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-rxc6-q384-2wrxIN-MAL-2026-012908

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks routerbase-mcp-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