T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Remote Dependencies and Mutable Installation Sources
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent EV charger lookup integration, but users should understand it sends search and location data to Camino AI and uses mutable install commands.
Install only if you are comfortable using Camino AI as a third-party service for EV charger searches. Prefer a pinned install source when possible, store the API key with appropriate local permissions, and avoid sending precise home or sensitive trip locations unless you accept that those query details are transmitted to Camino AI.
SKILL.md:10Unpinned Remote Dependencies and Mutable Installation Sources
scripts/ev-charger.sh:34Unvalidated URL Parameters Permit Curl URL Globbing and Query Manipulation
The skill instructs users to place an API key into ~/.claude/settings.json, which is a sensitive agent configuration location. Modifying this directory can affect broader agent behavior and may expose secrets to other skills, logs, backups, or unintended tooling if access controls are weak.
Add your key to Claude Code:
Add to your ~/.claude/settings.json:
{
The skill includes shell-based installation and execution instructions but does not declare any explicit tool scope or allowed-tools boundaries. In an agent setting, this can lead to over-broad shell access being assumed or granted, increasing the chance that the skill is run with more capability than necessary.
Using npx skills add https://github.com/barneyjm/camino-skills without pinning a version, tag, or commit means the installed code can change over time. If the upstream package or referenced repo is compromised, users may fetch and execute unexpected code during installation.
Installing a specific skill from an unpinned GitHub source still leaves users exposed to supply-chain changes in the repository state. A later malicious or accidental change could alter the skill content or associated scripts without the user realizing it.
npx clawhub@latest install ev-charger explicitly tracks the latest version, which is mutable and could introduce malicious or breaking changes at any time. This is a classic supply-chain risk because execution happens before the user can meaningfully review what changed.
The setup flow asks the user to transmit an email address to a third-party API endpoint to obtain a trial key, but it gives no privacy notice or data-handling explanation. This creates a privacy and compliance risk because users may disclose personally identifiable information without understanding retention, sharing, or consent implications.
This command sends user-provided email data to an external service endpoint. Even though this is part of normal product setup, it is still an external data transmission and should be treated as sensitive because it shares personal information outside the local environment.
Instant Trial (no signup required): Get a temporary API key with 25 calls:
curl -s -X POST -H "Content-Type: application/json" \
-d '{"email": "you@example.com"}' \
https://api.getcamino.ai/trial/start
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST -H "Content-Type: application/json" \
-d '{"email": "you@example.com"}' \
https://api.getcamino.ai/trial/start
Returns: {"api_key": "camino-xxx...", "calls_remaining": 25, ...}
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST -H "Content-Type: application/json" \
-d '{"email": "you@example.com"}' \
https://api.getcamino.ai/trial/start
Returns: {"api_key": "camino-xxx...", "calls_remaining": 25, ...}
The script transmits user-supplied query and location fields such as lat, lon, and radius to a third-party Camino API, but the script itself provides no user-facing notice that precise destination or route-adjacent location data will leave the local environment. In a skill context, this is a genuine privacy issue because location data can be sensitive, and users or calling agents may not realize the data is being disclosed externally.
The script makes an outbound request to https://api.getcamino.ai/query and includes user-derived parameters in the URL query string, along with an API key in a header. External transmission is expected for this skill's functionality, but it is still a true data exposure boundary because sensitive location/search data is sent to a remote service and may be logged by intermediaries or the provider.
curl -s -X GET \
-H "X-API-Key: $CAMINO_API_KEY" \
-H "X-Client: claude-code-skill" \
"https://api.getcamino.ai/query?${QUERY_STRING}" | jq .