Back to skill

Security audit

数联互通weather

Security checks for vulnerabilities and agentic risk

Overview

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.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:43
Finding

WeatherAPI Credential Exposure Through Plaintext Configuration, Process Arguments, and Diagnostic Output

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

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.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 84)May include surrounding context.

bash
API_KEY="${WEATHER_API_KEY}"
curl -s "https://api.weatherapi.com/v1/current.json?key=${API_KEY}&q=London"

Forecast

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 91)May include surrounding context.

bash
API_KEY="${WEATHER_API_KEY}"
curl -s "https://api.weatherapi.com/v1/current.json?key=${API_KEY}&q=London"

Forecast

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 98)May include surrounding context.

bash
API_KEY="${WEATHER_API_KEY}"
curl -s "https://api.weatherapi.com/v1/current.json?key=${API_KEY}&q=London"

Forecast

Static analysis

Detected: suspicious.generated_source_template_injection

User-controlled placeholder is embedded directly into generated source code.

Critical
Code
suspicious.generated_source_template_injection
Location
SKILL.md:83