T08 · Insecure Dependencies
- Location
SKILL.md:9- Finding
Unpinned Third-Party Package Installation in a Redirect-Only Skill
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 9–13
Vulnerability Type: Unpinned third-party Node.js dependency
Risk Level: MediumVulnerable Code:
yaml requires: bins: [gsd] install: kind: node package: gsd-pi bins: [gsd]Technical Analysis
The skill metadata permits installation of the third-party Node.js package
gsd-piwithout specifying an exact version, integrity digest, or otherwise verifiable source. Dependency resolution can therefore select a package release that differs from the version reviewed by the skill publisher or auditor.This creates a supply-chain risk because Node.js package installation can invoke package lifecycle scripts and install executable content. If the package registry account, package release process, or resolved package version is compromised, attacker-controlled code could run during installation with the privileges of the user or service installing the skill.
The dependency is also inconsistent with the skill's stated purpose. The document describes itself as a name reservation and directs users to install
gsd-orchestrator; consequently, automatically provisioninggsd-piexpands the trusted computing base without an evident functional requirement.Attack Path
- A user or automation system installs or processes the
gsd-headlessskill. - The skill manager observes that the required
gsdbinary is unavailable. - The unpinned
gsd-pipackage is resolved from the configured Node.js package source. - An unexpectedly changed or compromised package release is downloaded.
- Package lifecycle scripts or installed executable code run with the privileges of the installing process.
- Malicious package behavior could then access resources available to that account.
Exploitation depends on compromise or malicious modification of the dependency or its distribution channel; no malicious payload was present in the audited pr ...[truncated 608 chars]
- A user or automation system installs or processes the
- Remediation
View remediation
Remediation Suggestions
- Remove the
requiresandinstallmetadata from this skill if it is solely a name reservation and redirect. - If
gsd-piis genuinely required, pin it to a reviewed exact version rather than allowing unconstrained resolution. - Enforce integrity verification through a trusted lockfile, package digest, or equivalent mechanism supported by the installation framework.
- Disable or restrict package lifecycle scripts where operationally possible.
- Document the package's purpose, trusted registry, publisher, reviewed version, and update procedure.
- Perform dependency installation with a least-privileged account and isolate it from sensitive credentials and host resources.
- Continuously monitor the dependency for ownership changes, compromised releases, known vulnerabilities, and unexpected lifecycle-script modifications.
- Remove the
