T09 · Insecure Skill Coding Practices
- Location
weather.sh:25- Finding
Amap API Key Exposed Through Process Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Amap weather lookup helper with some privacy and API-key handling caveats, but no evidence of hidden or destructive behavior.
Install only if you are comfortable using Amap for weather lookups and sharing queried city or coordinate data with Amap. Use a restricted, low-quota AMAP_API_KEY where possible, avoid precise coordinates unless needed, and rotate the key if process logs or monitoring systems may capture command-line arguments.
weather.sh:25Amap API Key Exposed Through Process Command-Line Arguments
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
curl -X GET "https://restapi.amap.com/v3/weather/weatherInfo?city=BEIJING&key=YOUR_API_KEY&output=json"
The skill includes executable shell examples and a quick-start script but does not declare any explicit tool scope or allowed tools. In agent environments, missing tool restrictions can allow broader-than-intended shell access, increasing the chance of command execution beyond the narrow weather lookup use case.
The skill sends user-supplied city names or coordinates to Amap but does not clearly disclose that this data is transmitted to a third-party service. This creates a privacy and transparency issue, especially for precise location data, even though the transmitted data is limited to weather-query parameters.
No suspicious patterns detected.