T08 · Insecure Dependencies
- Location
SKILL.md:39- Finding
Unpinned Global Installation of Third-Party CLI Packages
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:39
Vulnerability Type: Unpinned third-party dependency installed with global scope
Risk Level: HighVulnerable Code Snippet
bash brew install tidyapp/tap/tidy-request # or: npm i -g @tidydotcom/cliTechnical Analysis
The Skill instructs users to install and execute the latest available version of a third-party CLI through either a Homebrew tap or npm. Neither installation command pins a reviewed version or verifies a checksum, package signature, or source commit.
The npm alternative installs the package globally. Package installation can execute lifecycle scripts, while the installed CLI subsequently runs with the invoking user's permissions. The Homebrew alternative similarly trusts mutable package definitions and upstream artifacts.
This creates a supply-chain trust boundary that extends beyond the audited Skill files. If the package publisher account, package registry entry, Homebrew tap, dependency graph, or release infrastructure is compromised, the command could install code materially different from what was reviewed. The package would also be positioned to access the
TIDY_API_TOKENenvironment variable and the documented TIDY credential file when invoked.No evidence was found that the referenced packages are currently malicious. The vulnerability is the unsafe, unpinned installation mechanism and absence of integrity controls.
Attack Path
- An attacker compromises the npm publisher account, Homebrew tap, release infrastructure, or an upstream package dependency.
- The attacker publishes a malicious release under the package name referenced by the Skill.
- A user follows the documented installation command without specifying a trusted version.
- The package manager retrieves the attacker-controlled release.
- Malicious package lifecycle logic or CLI code executes with the user's local privileges.
- The malicious code ...[truncated 830 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version rather than installing the latest available release.
- Publish and document cryptographic checksums or verifiable package signatures for approved artifacts.
- Link to the canonical source repository and identify the reviewed release tag or commit.
- Avoid global npm installation where possible. Prefer an isolated environment, a locked project dependency, or a verified standalone binary.
- Document whether npm lifecycle scripts are required. If they are not, recommend installation with lifecycle scripts disabled.
- Use lockfiles and integrity metadata for all transitive dependencies.
- Establish dependency monitoring and require re-review before updating the pinned version.
- Advise users to run the CLI with only the filesystem and environment access required for TIDY operations.
