T09 · Insecure Skill Coding Practices
- Location
SKILL.md:43- Finding
WeatherAPI Credential Exposure Through Plaintext Configuration, Process Arguments, and Diagnostic Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This weather skill is coherent and purpose-aligned, but users should handle the required WeatherAPI key carefully.
Use the OpenClaw UI or a protected secret store if available, restrict permissions on any file containing the WeatherAPI key, avoid committing dotfiles or config files with the key, and do not share logs, curl commands, or configuration output unless the key is redacted. Rotate the WeatherAPI key if it may have been exposed.
SKILL.md:43WeatherAPI Credential Exposure Through Plaintext Configuration, Process Arguments, and Diagnostic Output
The documentation tells users to store an API key in a plaintext config file or shell startup file, but does not warn about local credential exposure, file permissions, shell history, backups, or accidental disclosure. While common in developer tooling, this still increases the chance that secrets are leaked to other local users, support bundles, dotfile repos, or malware on the host.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
API_KEY="${WEATHER_API_KEY}"
curl -s "https://api.weatherapi.com/v1/current.json?key=${API_KEY}&q=London"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
API_KEY="${WEATHER_API_KEY}"
curl -s "https://api.weatherapi.com/v1/current.json?key=${API_KEY}&q=London"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
API_KEY="${WEATHER_API_KEY}"
curl -s "https://api.weatherapi.com/v1/current.json?key=${API_KEY}&q=London"
Detected: suspicious.generated_source_template_injection