# MAL-2026-11480: Malicious code in routerbase-mcp (npm)


- **Type:** Malicious package
- **Package:** `routerbase-mcp` (npm)
- **Published:** 31 Jul 2026
- **Also known as:** GHSA-rxc6-q384-2wrx

## What is MAL-2026-11480?

MAL-2026-11480 is a malicious package in routerbase-mcp, published on 31 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-11480?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11480 is a malicious package: routerbase-mcp (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11480/ (Markdown: https://insights.sbomify.com/MAL-2026-11480/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11480

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11480/
Summaries are generated and may contain mistakes; the official description above is the record.