T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Execution of an Unpinned Third-Party Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 17–33
Vulnerability Type: Unpinned dependency execution
Risk Level: MediumThe documented commands execute the
agent-chatpackage without specifying an audited version, cryptographic hash, or lockfile.bash uv run --with agent-chat agent-chat serve --password SECRET --tunnel cloudflared uv run --with agent-chat agent-chat join --url https://xxx.trycloudflare.com --password SECRET --agent-name "my-agent" uv run --with agent-chat agent-chat send --url https://xxx.trycloudflare.com --password SECRET --agent-name "my-agent" --message "hello!" uv run --with agent-chat agent-chat listen --url https://xxx.trycloudflare.com --password SECRETTechnical Analysis
The
uv run --with agent-chatinvocation dynamically resolves, downloads, and executes a third-party package from the configured package index. Because no package version, artifact hash, or verified lockfile is provided, the effective code executed by these commands can change after this Skill has been reviewed.This creates a supply-chain trust boundary outside the audited project. If the package publisher account, package registry, dependency resolution process, or a transitive dependency is compromised, following the documented instructions could execute attacker-controlled code. The audit found no evidence that the currently published package is malicious; the vulnerability is the mutable and unverified dependency execution mechanism.
Attack Path
- An attacker compromises the
agent-chatdistribution channel, publisher account, package registry, or a dependency selected during resolution. - The attacker publishes a modified package version containing malicious installation-time or runtime behavior.
- A user follows one of the documented
uv run --with agent-chatcommands. uvresolves and downloads the unpinned package or affected dependency.- The downloaded package ...[truncated 699 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
agent-chatto a specific version that has been reviewed and tested. - Use a committed lockfile with cryptographic hashes for the package and all transitive dependencies.
- Configure
uvto use an explicitly trusted package registry rather than relying on ambient index configuration. - Verify package provenance or signatures where supported.
- Periodically review pinned updates before changing the approved version.
- Run the package with least privilege, preferably in an isolated environment with restricted filesystem, credential, and network access.
- Document the expected package publisher, registry, version, and integrity information so users can verify the resolved artifact before execution.
- Pin
