T08 · Insecure Dependencies
- Location
SKILL.md:29- Finding
Unpinned Remote Dependency Execution and Broad Dependency Updates
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 29-41
Vulnerability Type: Supply-chain risk through mutable remote packages and unscoped updates
Risk Level: HighVulnerable Code
bash Install/refresh with ClawHub: npx -y clawhub@latest install topic-monitor npx -y clawhub@latest install polymarket-odds npx -y clawhub@latest install simmer-weather npx -y clawhub@latest update --all Verify: npx -y clawhub@latest listTechnical Analysis
The instructions use
npx -y clawhub@latest, which can download and execute the current registry version of theclawhubpackage without pinning it to the version that was reviewed. The-yoption suppresses interactive confirmation, while@latestallows the executed implementation to change after this Skill has been audited.The three installed Skills are also requested without exact version constraints, even though
SKILL.mdidentifies specific inspected versions (topic-monitor1.3.4,polymarket-odds1.0.0, andsimmer-weather1.7.1). Consequently, the installed code is not guaranteed to match the reviewed versions.The
update --allcommand further exceeds the minimum dependency-management scope required by this Skill. It can modify unrelated locally installed Skills rather than updating only the three declared dependencies. This enlarges the supply-chain attack surface and may unexpectedly change other agent functionality.Attack Path
- An attacker compromises the package registry account, distribution channel, or a future release of
clawhubor one of the named Skills. - The compromised release becomes the version resolved by
@latestor by an unversioned Skill installation. - A user follows the documented installation or verification commands.
npxdownloads and executes the changedclawhubpackage with the invoking user's privileges.- The installer installs changed upstream Skill code, or
update --allre ...[truncated 1267 chars]
- An attacker compromises the package registry account, distribution channel, or a future release of
- Remediation
View remediation
Remediation Suggestions
- Pin the ClawHub CLI to an exact reviewed version instead of using
@latest, for example:bash npx -y clawhub@<reviewed-version> ... - Pin each upstream Skill to the exact inspected version:
topic-monitor1.3.4polymarket-odds1.0.0simmer-weather1.7.1
- Verify package integrity using trusted checksums, lockfiles, signatures, or registry provenance before execution.
- Remove
update --all. Update only explicitly named dependencies after reviewing their release contents and integrity metadata. - Avoid automatic confirmation with
-ywhere practical so users can review package-resolution details before remote code executes. - Run installation and dependency inspection in a sandbox or least-privileged environment without trading credentials in the process environment.
- Expose
SIMMER_API_KEYonly to the specific execution process that requires it, rather than to installation, update, market-query, or monitoring commands. - Re-audit upstream Skills whenever their pinned versions change.
- Pin the ClawHub CLI to an exact reviewed version instead of using
