T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Package Execution During Global Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 16
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code Snippet:
bash npx skills add nexscope-ai/eCommerce-Skills --skill etsy-seo -gTechnical Analysis
The documented installation command invokes the
skillsnpm package throughnpxwithout specifying an exact version or integrity constraint. Consequently, installation can retrieve and execute whichever package version the configured registry resolves at that time. The-goption also causes the Skill to be installed globally.This creates a supply-chain risk because the code executed during installation can differ from the code reviewed in this audit. If the package account, package registry, dependency chain, or a future package release is compromised, the installation command could execute attacker-controlled package CLI or lifecycle code with the privileges of the user running
npx.No malicious behavior was found in the reviewed local Python implementation. In particular,
scripts/analyzer.pycontains no network requests, subprocess execution, dynamic evaluation, sensitive-file access, credential collection, persistence mechanisms, or data-exfiltration behavior. The vulnerability is limited to the unsafe, unpinned installation procedure documented inSKILL.md.Attack Path
- An attacker compromises the npm package, its maintainer account, its dependency chain, or the registry resolution path.
- The attacker publishes or causes resolution to a malicious version of the unpinned
skillspackage. - A user follows the documented command and executes
npx skills .... npxdownloads and runs the currently resolved package code without enforcing a reviewed version or integrity hash.- Malicious CLI or lifecycle code executes under the installing user's account.
- The malicious package may access data available to that user, ...[truncated 845 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the installer package to a specific, audited version rather than relying on the latest registry resolution:
bash npx --yes skills@<audited-exact-version> add nexscope-ai/eCommerce-Skills --skill etsy-seo - Verify the selected package version and its dependency tree before publication of the installation instructions.
- Use a lockfile-backed installation workflow and enforce package integrity hashes where supported.
- Document the expected package registry and prevent fallback to untrusted or unexpected registries.
- Avoid global installation unless it is operationally necessary. Prefer a project-local installation performed under a non-privileged account.
- Advise users not to run the installation command with
sudo, root, or administrator privileges. - Consider distributing a reviewed, versioned installer artifact whose checksum or signature can be independently verified.
- Pin the installer package to a specific, audited version rather than relying on the latest registry resolution:
