# MAL-2026-5485: Malicious code in mcp-server-supabase (npm)


- **Type:** Malicious package
- **Package:** `mcp-server-supabase` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-m633-5vq7-98qx

## What is MAL-2026-5485?

MAL-2026-5485 is a malicious package in mcp-server-supabase, published on 9 Jun 2026. 

### Official description

Package squats the unscoped name `mcp-server-supabase` to intercept `npx mcp-server-supabase` invocations intended for the official scoped Supabase Model Context Protocol server. `package.json` declares `"postinstall": "node index.js"`, and `index.js` collects `os.hostname()`, `os.platform()`, `process.cwd()`, `npm_config_user_agent`, and Node.js version, then POSTs them to `https://npx-canary-log.vulnerable-live.workers.dev/log` (hardcoded at index.js:16). Every install or `npx` invocation silently transmits installer host identifiers to an attacker-controlled Cloudflare Workers endpoint, with no consent, opt-out, or documentation prior to install. The name-confusion attack ensures AI coding agents and developer tooling that invoke the unscoped name are routed to this code instead of the legitimate scoped package.

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-5485?

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-5485 is a malicious package: mcp-server-supabase (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-5485/ (Markdown: https://insights.sbomify.com/MAL-2026-5485/index.md)
```

## Sources

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

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