T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Unpinned npx Installer Creates a Supply-Chain Execution Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:31-33; the same command also appears inREADME.md:8-10
Vulnerability Type: T08: Insecure Dependencies
Risk Level: MediumComplete vulnerable code snippet (
SKILL.md:31-33):bash npx skills add omactiengartelle/movie-poster-generatorEquivalent documented command (
README.md:8-10):bash npx skills add omactiengartelle/movie-poster-generatorTechnical Analysis
The documented installation procedure invokes
npx skillswithout pinning theskillspackage to a reviewed version or verifying its integrity. If the package is not already installed locally,npxcan resolve and download a mutable package from the configured npm registry and execute its command.Consequently, the code executed during installation is not limited to the project content reviewed in this audit. It may change after review because package resolution depends on the registry state and user configuration at installation time. This creates a supply-chain trust boundary around an unpinned executable dependency.
The command is not proof that the current package is malicious. The vulnerability is that compromise of the resolved package, its publisher, the registry account, or package resolution path could cause arbitrary code to run when a user follows the official installation instructions.
Attack Path
- An attacker compromises the publisher account or release process for the package resolved as
skills, or influences package resolution through a malicious registry configuration. - The attacker publishes a modified package version containing malicious installation or runtime code.
- A user follows the documented
npx skills add ...command. npxretrieves the current attacker-controlled version because no reviewed version or integrity value is specified.- The malicious package executes with the operating-system privileges of the user running the ...[truncated 516 chars]
- An attacker compromises the publisher account or release process for the package resolved as
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to a specifically reviewed version, for example by using an exact package version rather than allowing latest-version resolution.
- Publish and verify package integrity information or signatures before execution.
- Document the expected npm registry and publisher identity so users can detect unexpected package resolution.
- Prefer a trusted, already-installed installer instead of allowing
npxto download and immediately execute code. - Use lockfiles and automated dependency provenance checks where the installation workflow supports them.
- Periodically review the pinned installer version before updating it.
