T08 · Insecure Dependencies
- Location
SKILL.md:216- Finding
Unpinned Third-Party CLI Packages Installed Globally
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 216
Vulnerability Type: Unpinned and unverified third-party dependencies
Risk Level: MediumVulnerable Code
markdown ## CLI Alternative Install: `brew install tidyapp/tap/tidy-request` or `npm i -g @tidydotcom/cli`.Technical Analysis
The skill recommends installing third-party CLI packages from a Homebrew tap or the npm registry without pinning a reviewed version or verifying the downloaded artifact's checksum or signature. Both commands therefore resolve to whichever package release is current at installation time, allowing the installed implementation to change after this skill has been audited.
The npm command installs the package globally and may execute package lifecycle scripts under the invoking user's privileges. Because the package's source is not included in the audited project, its behavior—including installation hooks and handling of
TIDY_API_TOKEN—cannot be verified from this artifact.This creates a supply-chain trust boundary: compromise of the package publisher, registry account, npm package, Homebrew tap, or upstream distribution artifact could turn the documented installation command into a local code-execution vector.
Attack Path
- An attacker compromises the npm publisher account, Homebrew tap, upstream artifact, or another relevant distribution component.
- The attacker publishes a malicious release under the legitimate package name.
- A user follows the unpinned command in
SKILL.md. - The package manager retrieves the current compromised release because no version or digest is fixed.
- Malicious installation hooks or CLI code execute with the user's privileges.
- The payload can inspect user-accessible files and environment variables, potentially including
TIDY_API_TOKEN. - The stolen token may be used to perform authenticated TIDY API operations within the permissions granted to that token.
Impact Assessment
Successful expl ...[truncated 665 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specific, reviewed version rather than installing the latest mutable release.
- Publish trusted SHA-256 checksums or cryptographic signatures and require verification before installation.
- Link to the CLI's verifiable source repository and document the reviewed source revision corresponding to the pinned release.
- Prefer a project-local installation over a global npm installation to limit scope and improve reproducibility.
- Use least-privileged accounts or isolated environments when installing and running third-party tools.
- Disable npm lifecycle scripts during installation when they are not required, and explicitly document any scripts that must run.
- Apply minimum necessary permissions to
TIDY_API_TOKEN, keep it out of persistent shell configuration where practical, and rotate it immediately if package compromise is suspected.
