T08 · Insecure Dependencies
- Location
SKILL.md:111- Finding
Unpinned Third-Party Package Is Dynamically Retrieved and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:111-140
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
bash uvx desktop-agent screen size # ... uvx desktop-agent mouse move <x> <y> # ... uvx desktop-agent mouse right-clickbash uvx desktop-agent keyboard press down --presses 2 uvx desktop-agent keyboard press returnbash uvx desktop-agent keyboard press returnbash uvx desktop-agent mouse move 720 400 uvx desktop-agent mouse right-click sleep 1 uvx desktop-agent keyboard press down --presses 2 uvx desktop-agent keyboard press return sleep 1 uvx desktop-agent keyboard press returnTechnical Analysis
The skill directs the agent to invoke
desktop-agentthroughuvxwithout specifying an exact package version or an integrity-verified lock file.uvxcan resolve and execute a third-party Python package on demand. Consequently, the code executed during a future skill invocation may differ from the package version that existed when this document was reviewed.If the upstream package, package registry account, distribution channel, or a newly resolved release is compromised, attacker-controlled package initialization or command-handling code could run under the invoking user's operating-system account. The risk is amplified because the package is intentionally used for desktop interaction, including mouse and keyboard control.
No evidence establishes that the current
desktop-agentpackage is malicious. The confirmed issue is the unsafe, unpinned supply-chain execution pattern.Attack Path
- An attacker compromises the upstream package, its publisher account, or its distribution channel and publishes a malicious release.
- An agent follows
SKILL.mdand executes an unversioned command such asuvx desktop-agent screen size. uvxresolves and obtains the current p ...[truncated 936 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
desktop-agentto an exact, reviewed version in every invocation rather than allowing resolution of the latest release. - Manage the dependency through a committed lock file containing cryptographic hashes, and require hash verification during installation.
- Document and restrict the trusted package index or registry. Disable fallback to unapproved package sources.
- Prefer installing the reviewed dependency during a controlled provisioning phase instead of dynamically retrieving it while the skill runs.
- Execute desktop automation in a sandbox or isolated user account with minimal filesystem, environment-variable, network, clipboard, and application access.
- Maintain an allowlist of permitted desktop operations and require user confirmation before sensitive keyboard or mouse actions.
- Periodically review the pinned release and update it only after source, package metadata, publisher identity, and integrity checks have been completed.
- Pin
