T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Installer and Mutable Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–18
Vulnerability Type: Supply-chain risk caused by unpinned third-party dependencies
Risk Level: MediumVulnerable Code
markdown ## Installation ```bash npx skills add nexscope-ai/eCommerce-Skills --skill profit-margin-calculator-walmart -gtext ### Technical Analysis The documented installation command invokes the unversioned `skills` package through `npx` and installs Skill content globally from `nexscope-ai/eCommerce-Skills`. Neither the npm installer package nor the referenced Skill repository is pinned to an exact, audited version or immutable commit. When the package is not already available locally, `npx` may download and execute the currently published package. Consequently, the code executed during installation can differ from the version that was originally reviewed. The referenced Skill source is similarly mutable, creating an additional trust boundary in the installation chain. This finding concerns the installation instructions. The audited `scripts/calculator.py` itself contains no network requests, subprocess execution, persistence, credential access, or malicious embedded behavior. ### Attack Path 1. An attacker compromises, takes over, or otherwise gains publishing access to the `skills` npm package or the referenced Skill repository. 2. The attacker publishes a malicious package release or modifies the mutable repository content. 3. A user follows the documented installation command. 4. `npx` retrieves and executes the current unpinned installer package. 5. The installer retrieves or installs the current mutable Skill content with the invoking user's permissions. 6. Malicious installer logic or modified Skill files execute immediately or when the globally installed Skill is later invoked. ### Impact Assessment Successful exploitation could execute arbitrary code with the privileges of the user running the i ...[truncated 605 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsnpm package to an exact, reviewed version rather than relying on the current published release. - Pin the Skill source to an immutable commit hash or cryptographically signed release tag.
- Publish and verify checksums or signatures for both the installer and installed Skill artifacts.
- Use a lockfile and a trusted package registry with integrity verification where supported.
- Avoid global installation unless it is operationally necessary; prefer a project-local installation with least-privilege permissions.
- Review package lifecycle scripts and transitive dependencies before permitting execution.
- Document a verification procedure that users can perform before installation.
- Run installation in a sandbox or restricted environment when the provenance of dependencies cannot be independently verified.
- Pin the
