Which versions of mcp-server-supabase are malicious?

The following npm versions of mcp-server-supabase are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate mcp-server-supabase if I installed it?

Remove mcp-server-supabase from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is mcp-server-supabase part of a known attack campaign?

Yes — mcp-server-supabase is associated with the IN-MAL-2026-005218, IN-MAL-2026-005217 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect mcp-server-supabase in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking mcp-server-supabase and packages like it before any post-install script runs.

Malicious package

mcp-server-supabasenpm

Malicious code in mcp-server-supabase (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5485

Immediate action

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

npm uninstall mcp-server-supabase

What this malware does

Package name impersonates the official scoped Supabase MCP server. package.json declares "postinstall": "node index.js", which fires automatically on npm install and unconditionally POSTs installer metadata — os.hostname(), process.cwd(), process.env.npm_config_user_agent, Node version, and os.platform() — to a hardcoded Cloudflare Workers endpoint at https://npx-canary-log.vulnerable-live.workers.dev/log. The package ships no functionality consumers requested; its entire on-install effect is the outbound beacon. Installers resolved to this unscoped name get their hostname and working-directory path silently transmitted to third-party infrastructure without consent.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

08b416eb115aa1fc3bcf831a10dcb808fcaa66c0c5d8986fc10fe61ca901584d

fdd7519780160ab3a92639d54eab0a62f08b3d435e61276f4ba599c638c3cd40

Frequently asked questions

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

Campaign

IN-MAL-2026-005218IN-MAL-2026-005217

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection