@myelixlabs/synapse-mcp
Cuts AI token costs, eliminates hallucinated refactors and answers in <2ms — AST code-knowledge graph for Cursor, Claude Code, Windsurf, Warp, Continue & Zed. Runs fully local.
This report shows the evidence for @myelixlabs/synapse-mcp@3.6.3. 9 of 16 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource directly establishes both remote binary execution and silent mutation of multiple third-party/global AI-agent instruction files during postinstall. This meets the block policy regardless of the scanner similarity hint.
Decision evidence
public snapshot- package.json runs postinstall automatically.
- lib/install.js downloads a platform binary into ~/.synapse-mcp.
- lib/install.js executes the downloaded binary with --version.
- Pinned 3.6.3 downloads lack a SHA-256/signature check.
- postinstall appends MCP-first instructions to detected Gemini, Claude, Cursor, Windsurf, and Cline control files.
- Injected policy directs agents away from shell/file discovery toward Synapse.
- Node auth flow uses explicit device-code sign-in and stores credentials locally.
- The Node dashboard binds to 127.0.0.1.
Source & flagged code
14 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time source downloads a native archive from a fixed external host without transport verification, extracts it, and installs an executable payload.
package.jsonView on unpkg · L8Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
bin/synapse-mcp.jsView on unpkg · L45A single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/synapse-mcp.jsView on unpkg · L45Source file is highly similar to a previously finalized malicious package; route for source-aware review.
bin/synapse-mcp.jsView on unpkgSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
bin/synapse-mcp.js#virtual:normalized:round1View on unpkg · L614A manifest entrypoint or package-local install chain reaches command-output exfiltration behavior.
bin/synapse-mcp.js#virtual:normalized:round1View on unpkg · L614Source downloads or fetches remote code and executes it.
lib/service.jsView on unpkg · L25Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/service.jsView on unpkgSource creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.
lib/install.jsView on unpkg · L251Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/install.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/server.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/auth.jsView on unpkgFindings
Affected versions and remediation
This report applies to @myelixlabs/synapse-mcp@3.6.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing @myelixlabs/synapse-mcp@3.6.3. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.