T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned Global Installation of a Mutable Third-Party Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 13–19
Vulnerability Type: Supply-chain exposure through an unpinned dependency installed globally
Risk Level: MediumVulnerable Code:
markdown Install (always use latest): ```bash npm install -g @projitive/mcp@latest@projitive/mcpmust be kept up to date — outdated versions may be missing tools or contain bugs.text ### Technical Analysis The skill instructs the operator or agent to install the mutable `latest` release of `@projitive/mcp` globally. It does not pin a reviewed version, enforce package integrity, provide a lockfile, or require approval before installation. Because the MCP implementation is not included in this repository, its effective behavior cannot be determined from the audited files. The contents associated with the `latest` distribution tag can also change after this skill has been reviewed. Depending on npm behavior and package configuration, installation may execute package lifecycle scripts. A global installation increases the potential scope beyond the current project and makes the installed tool available to other repositories and sessions. No evidence establishes that the current `@projitive/mcp` package is malicious. The vulnerability is the unsafe, non-reproducible dependency acquisition process and the resulting supply-chain exposure. ### Attack Path 1. An attacker compromises the npm package, a maintainer account, publishing credentials, or the upstream release process. 2. The attacker publishes a malicious version and assigns it to the `latest` distribution tag. 3. An agent or operator follows the skill's mandatory installation instruction. 4. npm downloads and globally installs the attacker-controlled release without validation against a previously reviewed version or integrity value. 5. Malicious lifecycle code may execute during installation, or malicious behavior may run when the installed MC ...[truncated 829 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version. - Prefer a project-local dependency recorded in
package.jsonand a committed lockfile instead of a global installation. - Verify package provenance and integrity using registry integrity metadata, trusted publishing, signatures, or an approved internal artifact registry.
- Review the selected package version, including lifecycle scripts and transitive dependencies, before approving it.
- Disable lifecycle scripts during acquisition where operationally feasible, and run required setup separately after review.
- Require explicit operator approval before installing or upgrading external software.
- Execute the MCP server in a least-privileged sandbox with narrowly scoped filesystem and network access.
- Use a controlled update process that reviews and tests each new version before changing the approved pin.
- Replace
