T08 · Insecure Dependencies
- Location
SKILL.md:57- Finding
Third-Party Package Execution Through npx Without Enforced Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:57-83
Vulnerability Type: Third-party dependency and supply-chain risk
Risk Level: MediumVulnerable Code
bash npx skills add flowzap-xyz/flowzap-mcp --skill flowzap-diagramsbash # Claude Code claude mcp add --transport stdio flowzap -- npx -y flowzap-mcp@1.3.6 # Or add to .mcp.json / claude_desktop_config.json / cursor / windsurf config: { "mcpServers": { "flowzap": { "command": "npx", "args": ["-y", "flowzap-mcp@1.3.6"] } } }Technical Analysis
The installation instructions cause
npxto retrieve and execute code from external npm sources. The recommended skill-installation command does not pin theskillsCLI to a specific version. It also identifies skill content through a remote repository reference, allowing the retrieved content to differ over time.The MCP package is pinned to
flowzap-mcp@1.3.6, and the document provides npm integrity and shasum values elsewhere. These measures reduce exposure but do not eliminate it: the displayed commands do not automatically compare the downloaded package against the documented digest before execution. The reviewed artifact also does not contain the MCP implementation, so its stated filesystem, environment, and network restrictions cannot be independently verified by this audit.This is a supply-chain weakness rather than evidence that the named packages are currently malicious.
Attack Path
- An attacker compromises an npm package, package maintainer account, transitive dependency, registry delivery path, or referenced remote repository.
- The user follows the documented
npxinstallation or MCP configuration instructions. npxdownloads the externally controlled package content. The unpinned CLI may resolve to a release that did not exist when the skill was audited.- Package installation hooks or runtime code execute with the ...[truncated 1088 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every executable npm package to an exact reviewed version, including the
skillsCLI. - Replace direct
npxexecution with a controlled installation process using a committed lockfile andnpm ci. - Enforce integrity verification before execution rather than presenting digests only as optional manual checks.
- Vendor or mirror reviewed package artifacts in a trusted repository when operationally feasible.
- Disable or audit npm lifecycle scripts during installation, using
--ignore-scriptswhere compatible. - Run the MCP server in a sandbox with minimal filesystem access, a sanitized environment, no unnecessary credentials, and an outbound network allowlist limited to required FlowZap endpoints.
- Review the exact MCP package and its transitive dependency tree independently, since those implementations are outside this artifact.
- Require explicit user consent and redact secrets, credentials, tokens, personal data, and proprietary content before sending generated DSL to external validation or playground endpoints.
- Pin every executable npm package to an exact reviewed version, including the
