T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:16
- Finding
- Unpinned Package Execution During Global Installation## Vulnerability Details **File Location**: `SKILL.md:16` **Vulnerability Type**: Unpinned third-party dependency execution **Risk Level**: Medium ### Vulnerable Code ```bash npx skills add nexscope-ai/eCommerce-Skills --skill brand-protection-tiktok -g ``` ### Technical Analysis The documented installation procedure invokes the `skills` npm package through `npx` without specifying an exact version or integrity hash. Consequently, the package resolved and executed at installation time may differ from the version that existed when this Skill was audited. Because `npx` may download and execute package code, including lifecycle behavior, compromise of the resolved package, its dependencies, or the relevant package distribution account could introduce arbitrary code into the installation process. The `-g` option also requests global Skill installation, increasing the persistence and scope of unauthorized modifications within the user's Skill environment. The repository's local Python scripts do not themselves retrieve remote code, execute subprocesses, access credentials, write files, establish persistence, or exfiltrate data. The risk arises specifically from the documented external installation command. ### Attack Path 1. An attacker compromises the npm package resolved as `skills`, one of its transitive dependencies, or its publishing account. 2. The attacker publishes a malicious package version containing installation-time or runtime code. 3. A user follows the command documented in `SKILL.md`. 4. `npx` resolves and downloads the current unpinned package version. 5. The malicious package code executes with the privileges of the user running the installation. 6. The package can alter the globally installed Skill environment or perform any operation available to that user. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the installing user's privileges. Depending on that user's permissions, an attacker could re ...[truncated 465 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the installer to an exact, reviewed version rather than relying on the latest package resolution: ```bash npx --yes skills@X.Y.Z add nexscope-ai/eCommerce-Skills --skill brand-protection-tiktok ``` 2. Verify the selected package version and all transitive dependencies through a committed lockfile and package integrity metadata. 3. Publish and document expected package provenance, registry, maintainer identity, and cryptographic checksums or signatures. 4. Avoid global installation unless it is necessary. Prefer a project-local or isolated environment to reduce the blast radius. 5. Review lifecycle scripts and dependency changes before upgrading the pinned installer. 6. In security-sensitive deployments, obtain the installer from a trusted internal mirror and enforce package allowlisting and integrity verification.