Skip to main content
Scans/github/AIWerk/mcp-bridge

AIWerk/mcp-bridge

github

Share

Summary

AIWerk/mcp-bridge v2026-03-22 was classified as CRITICAL RISK with a risk score of 220. Sigil detected 14 findings across 156 files, covering phases including provenance, code patterns, network exfiltration, install hooks. Review the findings below before installing this package.

Package description: MCP Bridge — Multiplex your MCP servers into one interface. Works with Claude Desktop, Cursor, Windsurf, and any MCP client.

CRITICAL RISK(220)

v2026-03-22

22 March 2026, 23:52 UTC

by Sigil Bot

Risk Score

220

Findings

14

Files Scanned

156

Provenance

Findings by Phase

Phase Ordering

Phases are ordered by criticality, with the most dangerous at the top. Click any phase header to expand or collapse its findings. Critical phases are expanded by default.

install-npm-postinstall

CRITICAL

npm lifecycle script — runs automatically on install

repo/docs/universal-recipe-spec.md:132

    "version": "latest",                 // Version constraint (semver, "latest", or pinned)
    "preInstall": [],                    // Shell commands to run before install (rare, security-sensitive — see §9)
    "postInstall": [],                   // Shell commands to run after install (rare, security-sensitive — see §9)
Why was this flagged?

npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.

install-npm-postinstall

CRITICAL

npm lifecycle script — runs automatically on install

repo/docs/universal-recipe-spec.md:133

    "preInstall": [],                    // Shell commands to run before install (rare, security-sensitive — see §9)
    "postInstall": [],                   // Shell commands to run after install (rare, security-sensitive — see §9)
    "platforms": {                       // Platform-specific overrides (optional)
Why was this flagged?

npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.

Badge

Sigil scan badge for github/AIWerk/mcp-bridge

Markdown

[![Sigil Scan](https://sigilsec.ai/badge/github/AIWerk/mcp-bridge)](https://sigilsec.ai/scans/78524D3B-BCC4-44AE-B0D4-418CFD39C659)

HTML

<a href="https://sigilsec.ai/scans/78524D3B-BCC4-44AE-B0D4-418CFD39C659"><img src="https://sigilsec.ai/badge/github/AIWerk/mcp-bridge" alt="Sigil Scan"></a>

Run This Scan Yourself

Scan your own packages

Run Sigil locally to audit any package before it touches your codebase.

curl -sSL https://sigilsec.ai/install.sh | sh
Read the docs →Free. Apache 2.0.

Early Access

Get cloud scanning, threat intel, and CI/CD integration.

Join 150+ developers on the waitlist.

Get threat intelligence and product updates

Security research, new threat signatures, and product updates. No spam.

Other github scans

Believe this result is incorrect? Request a review or see our Terms of Service and Methodology.

Scanned bySigil Bot