T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Runtime Installation of Third-Party Dependencies
- Content
View full analysis
/dev/null || python -m pip install requests python -c "from playwright.sync_api import sync_playwright" 2>/dev/null || { python -m pip install playwright && python -m playwright install chromium; } ``` ### Technical Analysis The Skill directs the agent to install the latest available releases of `requests`, Playwright, and Playwright's Chromium artifact when they are absent. No exact versions, package hashes, lock file, trusted repository configuration, or artifact integrity checks are specified. Consequently, the effective code executed by the Skill can change after the Skill itself has been audited. Python packages may execute code during installation or when imported, while the downloaded browser is a native executable. A compromised upstream release, dependency-confusion condition, malicious package-index configuration, or compromised artifact distribution channel could introduce attacker-controlled code. ### Attack Path 1. An attacker compromises an upstream package release, transitive dependency, configured Python package index, or Playwright browser artifact. 2. The Skill runs in an environment where one or more required components are absent. 3. The dependency checks fail, causing the unpinned installation commands to execute. 4. The package manager resolves the mutable latest package or artifact from the affected source. 5. Malicious installation, import-time, or executable code runs with the same operating-system privileges as the agent. 6. The malicious component can access files, environment variables, network resources, and credentials available to that account. ### Impact Assessment Successful exploitation permits arbitrary code execution under the agent's current account. The affected scope includes the project works ...[truncated 267 chars]- Remediation
View remediation
