T08 · Insecure Dependencies
- Location
README.md:140- Finding
Unpinned Third-Party Package Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:140
Vulnerability Type: Unpinned remote package execution throughnpx
Risk Level: MediumVulnerable code:
bash npx skills add ting2tao/value-nvest-skillTechnical Analysis
The documented installation command invokes the remotely resolved
skillsnpm package throughnpxwithout specifying an exact version. The project does not provide a lockfile, package checksum, registry restriction, or other integrity control for this installer.Because
npxcan download and execute a package that is not already installed, the effective installer code may differ from the code reviewed during this audit. If the package, its dependencies, its publisher account, or the configured npm registry is compromised, following the documented command could execute attacker-controlled code.This exposure is limited to users who manually run the installation command; the audited Skill documentation does not execute it automatically.
Attack Path
- An attacker compromises the publisher account, package, dependency chain, or package-resolution source associated with the unpinned
skillspackage. - The attacker publishes a malicious version that contains installation-time or runtime code execution.
- A user follows the installation instructions in
README.mdand runs the documentednpxcommand. npxresolves and downloads the attacker-controlled package version.- The malicious package executes with the privileges and environment access of the user running the command.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. Depending on that user's permissions and environment, the malicious package could access user-readable files, source code, environment variables, development credentials, SSH material, and authenticated developer tooling. It could also modify files or establish pers ...[truncated 253 chars]
- An attacker compromises the publisher account, package, dependency chain, or package-resolution source associated with the unpinned
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to an exact, reviewed package version, for example:
bash npx --yes skills@<reviewed-version> add ting2tao/value-nvest-skill - Publish and verify the expected package integrity hash or signed provenance before execution.
- Document the trusted npm registry explicitly and recommend checking the resolved package identity and version.
- Maintain a lockfile where installation tooling supports one, and review both direct and transitive dependencies.
- Prefer a locally included, auditable installation mechanism that does not download mutable executable code at installation time.
- Recommend running installation with least privilege and without unnecessary secrets in the process environment.
- Pin the installer to an exact, reviewed package version, for example:
