T08 · Insecure Dependencies
- Location
SKILL.md:41- Finding
Unpinned Global Installation of a Mutable Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 41-48
Vulnerability Type: Unpinned global package installation and supply-chain exposure
Risk Level: MediumVulnerable Code
powershell npm list tencentads-cli -g 2>$nullIf the package is not installed, the Skill instructs the Agent to execute:
powershell npm install tencentads-cli@latest -gTechnical Analysis
The setup procedure installs the mutable
latestrelease oftencentads-cliwithout pinning an audited version or verifying package integrity or provenance. The-goption installs the dependency globally, extending its effects beyond the project directory.npm packages may execute lifecycle scripts during installation. Consequently, a compromised publisher account, malicious replacement package, or unexpectedly unsafe future release could execute code with the permissions of the user running the Agent. Because
latestcan resolve to different code over time, the effective dependency is not fixed to the version reviewed with this Skill.The dependency is relevant to the Skill's advertised functionality, but globally installing an unverified mutable release exceeds the minimum scope necessary. A local, pinned dependency would provide a narrower privilege and impact boundary.
Attack Path
- An attacker compromises the package publisher, registry entry, or release process for
tencentads-cli. - The attacker publishes a malicious version and assigns it the
latestdistribution tag. - The Skill's first-use check determines that the CLI is not installed.
- The Agent executes
npm install tencentads-cli@latest -g. - Malicious package code or an npm lifecycle script executes with the Agent user's privileges.
- The installed global package can subsequently affect this Skill and other workflows that invoke the same command.
Impact Assessment
Successful exploitation could permit arbitrary code e ...[truncated 372 chars]
- An attacker compromises the package publisher, registry entry, or release process for
- Remediation
View remediation
Remediation Suggestions
- Pin
tencentads-clito an exact, reviewed version rather than using@latest. - Record and verify package integrity metadata or a trusted checksum.
- Install the package locally in an isolated Skill directory instead of globally.
- Use a lockfile and a trusted, explicitly configured npm registry.
- Review package lifecycle scripts and use
--ignore-scriptswhen installation scripts are unnecessary. - Require explicit user approval before installing or upgrading executable dependencies.
- Establish a controlled update process in which new versions are audited before changing the pinned version.
- Pin
