T08 · Insecure Dependencies
- Location
clawhub.json:4- Finding
Unpinned Third-Party SDK Executes with Access to High-Value Trading Credentials
- Content
View full analysis
Vulnerability Details
File Location:
clawhub.json:4-11,SKILL.md:14,SKILL.md:66,SKILL.md:112-114, andtrader.py:52,trader.py:235-249
Vulnerability Type: Unpinned third-party dependency with access to trading credentials
Risk Level: MediumVulnerable Code
clawhub.json:4-11:json "requires": { "env": [ "SIMMER_API_KEY", "SOLANA_PRIVATE_KEY" ], "pip": [ "simmer-sdk" ] }SKILL.md:112-114:markdown `simmer-sdk` is published on PyPI by Simmer Markets. - PyPI: https://pypi.org/project/simmer-sdk/ - GitHub: https://github.com/SpartanLabsXyz/simmer-sdk - Publisher: hello@simmer.marketstrader.py:52:python from simmer_sdk.skill import load_config, update_config, get_config_pathtrader.py:235-249:python def get_client(live=True): """Lazy-init SimmerClient singleton.""" global _client if _client is None: try: from simmer_sdk import SimmerClient except ImportError: print("Error: simmer-sdk not installed. Run: pip install simmer-sdk") sys.exit(1) api_key = os.environ.get("SIMMER_API_KEY") if not api_key: print("Error: SIMMER_API_KEY environment variable not set") print("Get your API key from: simmer.markets/dashboard -> SDK tab") sys.exit(1) venue = os.environ.get("TRADING_VENUE", "kalshi") _client = SimmerClient(api_key=api_key, venue=venue, live=live) return _clientTechnical Analysis
The project declares
simmer-sdkwithout an exact version or package integrity hash. Consequently, installation can resolve to a newer or otherwise unexpected package release that was not part of this audit.The SDK is imported during module initialization and again when the trading client is constructed. It receives
SIMMER_API_KEYdirectly, while the ...[truncated 2488 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
simmer-sdkto a reviewed exact version, such assimmer-sdk==X.Y.Z, in both package metadata and installation documentation. - Use a lockfile or requirements file containing cryptographic hashes, and install with hash verification enabled.
- Review dependency updates before changing the pinned version. Use automated dependency scanning and provenance verification where available.
- Do not provide
SOLANA_PRIVATE_KEYto dry-run, configuration-display, position-display, or market-discovery processes that do not need wallet signing. - Prefer an isolated signer or hardware-backed signing service so the raw private key is not available to general SDK code.
- Use narrowly scoped, revocable API credentials with trading limits and venue restrictions.
- Run the Skill under a dedicated low-privilege operating-system account with restricted filesystem access and outbound network controls.
- Allow outbound traffic only to documented and trusted trading API endpoints.
- Replace calls to private SDK interfaces such as
_requestwith documented public methods to reduce compatibility and behavioral uncertainty during dependency updates. - Monitor trading activity and rotate both credentials immediately if dependency compromise is suspected.
- Pin
