T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Third-Party Package Installation with Global CLI Exposure
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent guide for a Circle Chain SDK and CLI, but users should be cautious because it relies on an external npm package for sensitive wallet and account operations.
Before installing, treat the npm package as the code you are trusting: prefer a reviewed pinned version, avoid global install unless you need the `circle` command, and do not enter account, wallet, or payment-password data until you are comfortable with the package provenance. Set an explicit gateway host or `CIRCLE_SKIP_GEO=1` if you do not want the SDK to contact the GeoIP service.
SKILL.md:10Unpinned Third-Party Package Installation with Global CLI Exposure
SKILL.md:128Automatic Disclosure of Public IP Address to an External GeoIP Service
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
| Export | Description |
|--------|------------|
| `getGatewayHttp()` | Resolve effective HTTP settings (defaults → Geo hint → user `http.config`). Returns object with `host`, `protocol`, `timeoutRead`, `timeoutWrite`, `retryCount`, `retryWaitTime`, `sslSupport`. |
| `mergeUserHttpConfig(updates)` | Write key/value pairs to `~/.ccl/http.config`. |
| `getUserHttpConfigPath()` | Return path to `~/.ccl/http.config`. |
| `clearGatewayHttpCache()` | Invalidate in-memory cache for config and Geo host hint. |
| `refreshGatewayHttpGeoCache()` | Force refresh GeoIP lookup (Node only). |
The skill documents that the SDK performs an automatic GeoIP lookup against a third-party service (https://ipwho.is/) and caches the result, but it does not clearly warn that this transmits the user's public IP and related request metadata off-device. In a security/privacy context, undocumented outbound disclosure can surprise users, violate privacy expectations, and create compliance risk, especially because it occurs automatically on first configuration resolution.