T08 · Insecure Dependencies
- Location
README.md:13- Finding
Unpinned Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 13-16
Vulnerability Type: Supply-chain exposure through unpinned package execution
Risk Level: MediumVulnerable Code Snippet:
markdown ### Via ClawHub ```bash npx skills add argos-product-research -g -ytext ### Technical Analysis The documented installation command invokes the `skills` package through `npx` without specifying an exact package version or verifying its integrity. If the package is not already available in the local cache, `npx` may retrieve the package selected by the configured npm registry at installation time. Consequently, the code executed can differ from the code that was reviewed. The `-y` option suppresses interactive confirmation, reducing the opportunity for users to inspect which package and version will execute. The `-g` option requests global skill installation, increasing the persistence and scope of any malicious skill content installed through the command. Exploitation depends on compromise or malicious control of the referenced npm package, its maintainer account, a transitive dependency, the configured package registry, or the package-resolution environment. The repository itself does not contain an embedded malicious payload, and the audit found no evidence that the current `skills` package is malicious. ### Attack Path 1. An attacker compromises the npm package, a maintainer account, a transitive dependency, or a registry used to resolve the unversioned `skills` package. 2. The attacker publishes a malicious release that is selected by the unpinned `npx skills` invocation. 3. A user follows the README and executes: `npx skills add argos-product-research -g -y` 4. `npx` downloads and runs the attacker-controlled package version without an explicit version constraint and with confirmation suppressed. 5. Malicious package lifecycle or runtime code executes with the privileges of the invoking user. ...[truncated 845 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the installer package to a reviewed exact version, for example:
bash npx --yes skills@<reviewed-exact-version> add argos-product-research -g - Do not use a floating tag such as
latest; update the pinned version only after reviewing the release and its dependency changes. - Prefer a package manager lockfile and a reproducible local installation workflow where feasible.
- Publish and verify package integrity information, provenance attestations, and cryptographic signatures.
- Remove
-yfrom the recommended command when unattended installation is unnecessary so users can review package-resolution prompts. - Avoid global installation by default. Document a user-local or project-local installation method and explain when global installation is required.
- Advise users not to run the installation command with administrator or root privileges.
- Use a trusted registry and consider constraining registry configuration explicitly for automated environments.
- Pin the installer package to a reviewed exact version, for example:
