T08 · Insecure Dependencies
- Location
SKILL.md:32- Finding
Unpinned Third-Party Installation Chain
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:32-35;README.md:12-16
Vulnerability Type: Unpinned third-party dependencies and mutable installation sources
Risk Level: MediumAffected code in
SKILL.md:bash ## Install ```bash npx skills add blammectrappora/vtuber-avatar-skilltext **Affected code in `README.md`:** ```bash ## Install **Via npx skills:** ```bash npx skills add blammectrappora/vtuber-avatar-skilltext ### Technical Analysis The documented installation command invokes `npx` without pinning the `skills` package to a reviewed version. The referenced skill is also identified without an immutable version, release tag, commit hash, or integrity checksum. `npx` can download and execute package code during installation. Because both the installer package and skill reference are mutable, the effective code executed by users can differ from the code covered by this audit. This creates a supply-chain exposure if the package registry account, source repository, maintainer credentials, package namespace, or a future release is compromised. No evidence establishes that the current upstream components are malicious. Exploitation depends on compromise or malicious modification of an upstream component. ### Attack Path 1. An attacker compromises the unpinned `skills` package, its publication account, the referenced skill repository, or another relevant upstream distribution channel. 2. The attacker publishes a modified release containing malicious installation or lifecycle behavior. 3. A user follows the documented `npx skills add blammectrappora/vtuber-avatar-skill` command. 4. `npx` retrieves the current mutable package release rather than a specifically audited artifact. 5. Attacker-controlled package or installation code executes in the user's environment. ### Impact Assessment Successful exploitation could permit arbitrary code execution with the privileges ...[truncated 450 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsinstaller to an explicitly reviewed version, for example by using a version-qualified package reference. - Pin the installed skill to an immutable release or commit hash where the installation mechanism supports it.
- Publish and verify cryptographic checksums or signed release provenance for distributed artifacts.
- Use a lockfile or equivalent integrity metadata for every third-party package involved in installation.
- Document the expected package publisher, source repository, version, and checksum so users can verify provenance.
- Avoid recommending elevated execution and explicitly instruct users not to run the installer with administrator or root privileges.
- Periodically review pinned upstream versions and update them only after auditing the corresponding artifacts.
- Pin the
