T08 · Insecure Dependencies
- Location
SKILL.md:32- Finding
Unpinned Third-Party Installation Command Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:32-34;README.md:12-15
Vulnerability Type: Unpinned third-party package and skill installation
Risk Level: MediumVulnerable Code
SKILL.md:32-34:bash ## Install ```bash npx skills add blammectrappora/watercolor-art-generatortext `README.md:12-15`: ```bash **Via npx skills:** ```bash npx skills add blammectrappora/watercolor-art-generatortext ### Technical Analysis The documented installation command invokes `npx` without pinning an exact version of the `skills` package. It also identifies the skill by a mutable owner/name reference rather than a fixed release, commit, or content-integrity hash. `npx` may download and execute package code from the configured npm registry. Consequently, the code executed during installation can differ from the artifact covered by this audit. Compromise of the npm package, registry resolution, publisher account, or remote skill release could introduce attacker-controlled installation behavior. This is a supply-chain exposure rather than evidence that the currently audited files contain malicious code. ### Attack Path 1. An attacker compromises the publisher account, package, registry resolution path, or mutable remote skill release. 2. The attacker publishes a modified package or skill containing malicious installation logic. 3. A user follows the documented `npx skills add` command. 4. `npx` retrieves the current mutable package version rather than a reviewed and integrity-pinned version. 5. The malicious package or installation logic executes with the privileges of the invoking user. ### Impact Assessment Successful exploitation could allow arbitrary code execution under the account running the installation command. Depending on that account's permissions, the attacker could access user files and credentials, modify installed skills, initiate network requests, or establish fur ...[truncated 129 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsCLI to an exact reviewed version, for example by specifying an immutable package version. - Pin the installed skill to an exact release or commit rather than a mutable owner/name reference.
- Use registry integrity hashes and a lockfile where supported.
- Document the expected package registry and publisher identity.
- Prefer installation from a reviewed local artifact when the audited files are already available.
- In controlled environments, preinstall the verified CLI instead of allowing
npxto download and execute packages dynamically. - Verify package signatures or checksums before installation where the ecosystem supports them.
- Pin the
