T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Unpinned Third-Party Financial Package Can Access Wallet Credentials and Funds
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:8-17; corroborating dependency declaration inmetadata.json:21-29
Vulnerability Type: Unpinned executable dependency with access to sensitive wallet credentials
Risk Level: HighVulnerable Code
SKILL.md:8-17:yaml requires: bins: - pip install: - kind: pip package: social-value extras: liquid bins: [] - kind: uv package: social-value extras: liquid bins: []metadata.json:21-29:json "install": { "pip": "social-value" }, "requires": { "python": ">=3.10" }, "dependencies": [ "breez-sdk-liquid>=0.11.0" ],Technical Analysis
The Skill directs the environment to install the mutable
social-valuepackage from an external Python package registry without an exact version, package hash, signature, or lockfile. It also declaresbreez-sdk-liquid>=0.11.0, which allows dependency resolution to select any compatible future release.The audited artifact contains only
SKILL.mdandmetadata.json; it does not include the installed package's implementation. Consequently, the executable code that handles the BIP39 mnemonic, Breez API key, wallet state, and real-value transactions cannot be verified from this artifact. Claims such as “no telemetry” therefore cannot be validated locally.This is particularly sensitive because the documentation instructs operators to expose
SOCIAL_VALUE_MNEMONICto the installed package. A BIP39 mnemonic provides control over the wallet. Any malicious or compromised package release selected during installation could read and exfiltrate that mnemonic, submit unauthorized transactions, or execute arbitrary code with the privileges of the Agent process.Attack Path
- An attacker compromises the package publisher account, package registry entry, build process, or an allowed transitive dependency.
- The attacker publishes a mal ...[truncated 1750 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
social-valueand every direct dependency to exact, reviewed versions rather than using an unconstrained package name or a lower-bound-only constraint. - Generate and commit a lockfile covering all transitive dependencies for each supported backend and Python version.
- Require package hashes during installation, such as through pip hash-checking mode, and reject artifacts whose integrity does not match the reviewed lockfile.
- Prefer signed releases, attestations, reproducible builds, and a controlled internal package mirror.
- Include or vendor the wallet implementation in the reviewed artifact so its credential access, network destinations, transaction authorization, and telemetry behavior can be audited.
- Run wallet code in a dedicated, least-privileged process or container with a strict network allowlist and no access to unrelated credentials or files.
- Use a newly generated wallet dedicated to this Skill; never provide a mnemonic that controls unrelated or high-value funds.
- Default to testnet and require explicit operator confirmation before enabling mainnet.
- Set a conservative, nonzero
SOCIAL_VALUE_MAX_BALANCEby default and enforce transaction-level and daily spending limits independently of the package. - Require explicit operator approval for transfers, withdrawals, new destinations, and transactions above a small threshold.
- Rotate the wallet mnemonic and move all remaining funds immediately if package compromise or mnemonic exposure is suspected; merely uninstalling the package is insufficient.
- Pin
