T08 · Insecure Dependencies
- Location
clawhub.json:4- Finding
Unpinned Executable Third-Party Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
clawhub.json, lines 4–8
Vulnerability Type: Unpinned third-party dependencies
Risk Level: Mediumjson "requires": { "pip": [ "simmer-sdk", "requests" ],Technical Analysis
The project installs
simmer-sdkandrequestswithout exact version constraints or integrity hashes. Consequently, future installations may retrieve different code than the versions originally reviewed.This is particularly sensitive because
simmer-sdkis imported and executed by the Skill, receives theSIMMER_API_KEY, communicates with the trading service, and can submit financial trades when live mode is enabled. A compromised package release, compromised maintainer account, malicious dependency update, or altered transitive dependency could therefore execute code with the same process privileges as the Skill.The audit found no evidence that either currently named package is malicious. The vulnerability is the absence of dependency version and integrity controls.
Attack Path
- An attacker compromises an upstream package, its publishing account, or one of its transitive dependencies.
- The attacker publishes a malicious version under the legitimate package name.
- A managed installation or update resolves the unpinned dependency to that malicious version.
- Python imports and executes the dependency when
clob_microstructure.pystarts. - The malicious package reads process-accessible data such as
SIMMER_API_KEY, intercepts SDK requests, modifies returned market information, or invokes trading operations. - The attacker exfiltrates the credential or causes unauthorized trades within the API key's permissions.
Impact Assessment
Successful exploitation would grant the malicious dependency the privileges of the Skill process. This includes access to environment variables, including
SIMMER_API_KEY; local files available to the process; netwo ...[truncated 303 chars]- Remediation
View remediation
Remediation Suggestions
- Pin each direct dependency to an exact, reviewed version, for example
package==x.y.z. - Generate a lock file that also fixes all transitive dependency versions.
- Require cryptographic hashes during installation, such as a hash-locked requirements file used with
pip --require-hashes. - Review package provenance, release history, maintainers, and artifacts before approving upgrades.
- Perform dependency vulnerability and malware scanning in CI and fail builds on unreviewed lock-file changes.
- Install from a controlled package index or approved artifact repository where feasible.
- Run the Skill under a dedicated, minimally privileged account with restricted filesystem and network access.
- Use a dedicated Simmer API key with minimum trading permissions, explicit spending limits, monitoring, and rapid revocation capability.
- Pin each direct dependency to an exact, reviewed version, for example
