T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:30
- Finding
- Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 30-34 **Vulnerability Type**: Unpinned executable dependency **Risk Level**: Medium ### Vulnerable Code ```markdown ## Setup ```bash pip install agent-service-agreements ``` ``` ### Technical Analysis The setup instructions install `agent-service-agreements` from PyPI without specifying an audited version or verifying an integrity hash. Consequently, the package contents resolved by this command can change after the Skill has been reviewed. Python packages may execute code during installation or when imported by the documented examples. This project does not contain the dependency's source code, a lockfile, package hashes, or other evidence that would allow the installed implementation to be compared with a reviewed release. Therefore, the security claims in the Skill—including no network access, telemetry, credential access, or access outside the working directory—cannot be independently verified from the audited artifact. This finding does not establish that the current PyPI package is malicious. The risk arises from trusting mutable, externally hosted executable content without version or integrity controls. ### Attack Path 1. An attacker compromises the publisher account, build pipeline, or distribution channel for the referenced PyPI package. 2. The attacker publishes a malicious or backdoored package release under the same package name. 3. A user follows the documented `pip install agent-service-agreements` instruction. 4. `pip` resolves and downloads the attacker-controlled release because no version or hash is required. 5. Malicious behavior executes during installation, package import, or use of the documented API. ### Impact Assessment Malicious dependency code would generally execute with the privileges of the user running `pip` or the Python examples. Depending on those privileges and the execution environment, it could read or modify ...[truncated 316 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to an explicitly reviewed version, for example: ```bash pip install agent-service-agreements==0.1.0 ``` 2. Verify package integrity using trusted hashes and an installation mode such as: ```bash pip install --require-hashes -r requirements.txt ``` 3. Commit a dependency lockfile or hashed requirements file that records the exact approved artifact and all transitive dependencies. 4. Link to or include the source corresponding to the pinned package release so the documented security claims can be audited. 5. Install the package inside an isolated, least-privileged virtual environment or container without unnecessary credentials, filesystem access, or network access. 6. Add automated dependency provenance, vulnerability, and release-integrity checks to the publication process.