T08 · Insecure Dependencies
- Location
SKILL.md:58- Finding
Unpinned Third-Party Dependency Installed at Runtime
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:58
Vulnerability Type: Supply-chain exposure through an unpinned runtime dependency
Risk Level: MediumComplete Snippet:
markdown - if you use the Python x402 client path, install the EVM extras, not only the base package: `pip install 'x402[evm]'`Technical Analysis
The Skill directs the agent to install
x402[evm]without an exact version, integrity hash, lockfile, or verified package source. The package and its transitive dependencies can therefore change between executions. Python package installation may also execute build-system hooks or other package-controlled code.This installation is especially sensitive because the dependency is intended to participate in payment signing. Malicious or compromised package code executing in the agent's context could attempt to access wallet material, signed payment payloads, bearer credentials, uploaded files, and other process-accessible data.
The finding does not establish that the current
x402package is malicious. The vulnerability is the mutable and unauthenticated dependency-installation process.Attack Path
- An attacker compromises the selected package, one of its transitive dependencies, or the relevant package distribution channel.
- The agent follows the Skill and runs
pip install 'x402[evm]'. - The package manager resolves a compromised or unexpectedly changed release because no version or artifact hash is constrained.
- Package-controlled code executes during installation or later import and use.
- The code accesses data available to the agent, potentially including wallet credentials, payment authorizations, storage bearer tokens, or selected upload files.
- The compromised component can disclose those assets or manipulate storage and payment operations.
Impact Assessment
Successful exploitation grants code execution with the privileges of the environment perfo ...[truncated 342 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency and every transitive dependency to reviewed versions.
- Require cryptographic hashes for downloaded artifacts, such as through a hash-locked requirements file.
- Retrieve packages only from an explicitly trusted repository.
- Build and review a locked environment before Skill execution rather than installing packages during a user task.
- Run payment tooling in a sandbox with minimal filesystem and network access.
- Keep private keys behind a dedicated signer interface so imported dependencies cannot read raw key material.
- Continuously scan and periodically re-review the locked dependency set.
