ClawHub
Back to skill

Security audit

Weather-Webcam-V2

Security checks for vulnerabilities and agentic risk

Overview

This weather-and-webcam skill is coherent and disclosed, but users should understand it contacts third-party services and keeps a webcam browser cookie session.

Install only if you are comfortable sharing requested locations with Open-Meteo, search providers, and webcam sites, and with the skill keeping cookies in a webcam browser session for those sites. Clear or isolate that session if you do not want retained browsing state.

A.I.G

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding
The declared description says the skill retrieves weather data from Open-Meteo and obtains a live webcam image for a requested location from Meteoblue or Windy. The supplied code does none of that: it only inspects document images in the current page and filters for webcam-like URLs. This is a materially different implementation and primary behavior, with no evidence of weather API access, location handling, or specific integration with Meteoblue or Windy. Therefore the description does not accurately represent the code chunk.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The description says it fetches weather and captures a webcam image, but it does not clearly warn that the skill will automatically download third-party content to local storage. This can create privacy, consent, and provenance issues because users may not expect automated retrieval and storage of images from external sites.

External Transmission

Medium
Category
Data Exfiltration
Content
- Execute `curl -s "https://geocoding-api.open-meteo.com/v1/search?name=[Location]&count=1&language=es&format=json"` to resolve city name to coordinates.

2.  **Get weather (Open-Meteo)**:
    - Execute `curl -s "https://api.open-meteo.com/v1/forecast?latitude=[Lat]&longitude=[Lon]&current=temperature_2m,relative_humidity_2m,apparent_temperature,weather_code,wind_speed_10m"` to get real-time data.

3.  **Search for Webcam**:
    - Web search for `site:meteoblue.com [Location] webcam` or `site:windy.com [Location] webcam`.
Confidence
84% confidence
Finding
The skill transmits user-supplied location data and derived coordinates to external services, and then performs third-party web search and browsing. In this context that data flow is expected for the feature, but it is still a real security/privacy concern because it shares user query context with outside services and expands exposure through browser automation.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The workflow instructs the agent to interact with third-party websites and accept cookie banners automatically, but gives no explicit warning or consent mechanism. Automatically accepting cookies and browsing external sites can expose browsing metadata, set tracking state, and perform actions on behalf of the user without their informed approval.

Natural-Language Policy Violations

Low
Confidence
95% confidence
Finding
The geocoding API call hard-codes `language=es`, which imposes a specific locale without offering user opt-in or explaining why Spanish is required. This is a natural-language locale policy issue because it constrains output behavior silently.

Static analysis

No suspicious patterns detected.