T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Third-Party npm Package Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 5
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumComplete Code Snippet:
yaml metadata: {"clawdbot":{"emoji":"📦","requires":{"bins":["mcporter"]},"install":[{"id":"node","kind":"node","package":"mcporter","bins":["mcporter"],"label":"Install mcporter (node)"}]}}Technical Analysis
The installation metadata identifies the npm package
mcporterwithout specifying an exact version or integrity hash. Consequently, installation may resolve to a future package release that was not represented by or reviewed during this audit.The project provides no lockfile, vendored package source, checksum, registry restriction, or other integrity control that binds installation to a known artifact. This creates a supply-chain exposure if the package publisher, npm account, publication pipeline, or package registry is compromised.
This finding does not establish that the current
mcporterpackage is malicious. The risk arises from allowing a mutable third-party release to become part of the trusted execution environment without version or integrity verification.Attack Path
- An attacker compromises the npm package publisher, release pipeline, or registry distribution path for
mcporter. - The attacker publishes a malicious release under the expected package name.
- A user or automated Skill installer processes the metadata and installs
mcporterwithout an exact version constraint. - The package manager resolves the attacker-controlled release.
- Malicious code executes through package lifecycle scripts, when the installed CLI is invoked, or both.
- The payload operates with the privileges of the installing or invoking user and may access resources available to that account.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the privileges of the user who installs or invokes ...[truncated 681 chars]
- An attacker compromises the npm package publisher, release pipeline, or registry distribution path for
- Remediation
View remediation
Remediation Suggestions
- Pin
mcporterto an exact version that has been reviewed and approved rather than allowing the package manager to select a mutable release. - Record and verify the package artifact's integrity hash where the installation framework supports integrity validation.
- Add a lockfile or equivalent immutable dependency manifest if dependency resolution occurs within this project.
- Restrict installation to an explicitly trusted registry and reject unexpected registry overrides.
- Review the selected package version, including npm lifecycle scripts and transitive dependencies, before approval.
- Use an automated dependency-update process that requires security review before changing the pinned version or integrity value.
- Perform installation with least privilege and disable package lifecycle scripts when they are unnecessary.
- Run the CLI in a constrained environment with only the files, credentials, and network access required for its intended operation.
- Pin
