T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned and Unverifiable npm Runtime Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:9-14andSKILL.md:40-42
Vulnerability Type: Unpinned third-party dependencies and missing dependency integrity metadata
Risk Level: MediumVulnerable Code
yaml "install": [ { "id": "node", "kind": "node", "package": "@modelcontextprotocol/sdk", "label": "Install MCP runtime dependencies (run npm install in bundle root)", }, ],markdown - Install package dependencies in the bundle root before running runtime scripts: - `npm install` - Required packages are declared in `package.json` (`@modelcontextprotocol/sdk`, `zod`).The audited project does not contain the referenced
package.jsonor an npm lockfile. The installer metadata also identifies@modelcontextprotocol/sdkwithout an exact version, whilescripts/runtime/contract.mjsdirectly imports the additionalzoddependency.Technical Analysis
The package cannot establish which dependency versions and transitive components were reviewed. An unpinned package reference can resolve to a different release as the registry changes, and the absence of a lockfile prevents integrity-controlled, reproducible installation.
This is a supply-chain weakness rather than evidence that the currently named package is malicious. However, installing mutable dependencies allows a compromised future package release, compromised transitive dependency, or registry-account takeover to introduce code that was not part of this audit.
npm packages may execute lifecycle scripts during installation. Such scripts run with the privileges of the user or automation process performing the installation. The runtime also executes the installed SDK when the MCP server starts.
Attack Path
- An operator installs the Skill and follows its dependency installation instructions, or the marketplace installer processes the unversioned
packagefield. - npm resolves the package and its transitive dependencies us ...[truncated 1405 chars]
- An operator installs the Skill and follows its dependency installation instructions, or the marketplace installer processes the unversioned
- Remediation
View remediation
Remediation Suggestions
- Include a minimal, reviewed
package.jsondeclaring exact versions of both@modelcontextprotocol/sdkandzod. - Include the corresponding
package-lock.jsonin the published bundle. - Replace
npm installwithnpm ciso installation uses the exact lockfile graph and fails when metadata is inconsistent. - Pin the installer metadata to an exact reviewed package version rather than allowing mutable latest-version resolution.
- Review transitive dependencies and npm lifecycle scripts before publication.
- Use a trusted registry and retain npm integrity hashes in the lockfile.
- Consider installing with lifecycle scripts disabled where compatible:
bash npm ci --ignore-scripts- Run the MCP server as an unprivileged user in an environment with outbound network access disabled, preserving the declared offline-only boundary even if a dependency is compromised.
- Include a minimal, reviewed
