T08 · Insecure Dependencies
Warning
- Location
- README.md:27
- Finding
- Unpinned Third-Party Installer Creates a Supply-Chain Execution Risk## Vulnerability Details **File Location**: `README.md`, lines 27–29 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium **Vulnerable code snippet**: ```bash npx add https://github.com/wpank/ai/tree/main/skills/testing/reducing-entropy ``` ### Technical Analysis The documented installation procedure invokes the npm package named `add` through `npx` without pinning its package version or integrity hash. If that package is absent locally, `npx` may retrieve and execute it from the configured npm registry. The installer also receives a URL referencing mutable content in a personal GitHub repository. The URL does not pin the source to a reviewed commit, immutable release artifact, checksum, or cryptographic signature. Therefore, both the installer behavior and installed content may differ from what was reviewed during this audit. This is a supply-chain weakness rather than evidence that the currently documented package or repository is malicious. ### Attack Path 1. An attacker compromises the npm package, its publisher account, the configured package registry, the GitHub account, or the upstream repository. 2. The attacker publishes a malicious installer version or modifies the content referenced by the mutable repository URL. 3. A user copies and runs the documented `npx add ...` command. 4. `npx` retrieves and executes the unpinned installer under the user's account. 5. The compromised installer accesses or modifies resources available to that user, or installs altered Skill instructions that affect subsequent Agent behavior. ### Impact Assessment Successful exploitation could execute arbitrary code with the permissions of the user running the installation command. Depending on that user's environment, the resulting scope may include: - Reading or modifying files accessible to the user. - Altering project or user-level Agent configuration. - Installing malicious or modified Skill instru ...[truncated 388 chars]
- Remediation
- ## Remediation Suggestions 1. Replace the unversioned `npx add` invocation with a trusted installer pinned to an exact package version. 2. Pin the Skill source to a reviewed Git commit or immutable release tag rather than a mutable branch. 3. Publish and verify a cryptographic checksum or signature for the downloaded artifact. 4. Use `npx --no-install` when relying on an installer that must already be installed and independently verified. 5. Prefer a transparent installation process that downloads a fixed archive, verifies its digest, and copies only the expected files. 6. Document the exact expected files and hashes so users can validate the installed content. 7. Run installation with least privilege and avoid exposing unrelated credentials or sensitive environment variables to the installer.