Back to skill

Security audit

dayrelay-weather

Security checks for vulnerabilities and agentic risk

Overview

The scanners classify this weather skill as benign because the reported external request aligns with its weather purpose, while noting a timezone behavior concern and incomplete inspection.

The verdict is benign, not risk-free. Before installing, consider that the skill contacts Open-Meteo and may use UTC if no timezone is provided. Inspection was partial: one of two components was fully inspected and one was partially inspected, with a degraded tool-misuse analyzer, so the evidence is incomplete.

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
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 (3)

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% 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 46)May include surrounding context.

md
The helper reformats the provider data; it does not produce an independent forecast.
The data licence link is returned in the output as well.

The helper contacts only `https://api.open-meteo.com/v1/forecast`, with bounded
coordinates, fixed forecast fields, no redirects, and a request deadline. It rejects
unsupported CLI flags, stale/wrong-day responses, unit mismatches, and malformed data.
Network/provider errors return a short error code and a nonzero exit status. Report

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% 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 · scripts/weather.mjs (reported line 5)May include surrounding context.

js
// API contract adapted from https://open-meteo.com/en/docs - request a small daily
// forecast and normalize it for a briefing; no upstream implementation is copied.
const ENDPOINT = "https://api.open-meteo.com/v1/forecast";
const DAILY = ["weather_code", "temperature_2m_max", "temperature_2m_min",
  "precipitation_probability_max", "wind_speed_10m_max"];

The manifest requires an explicitly supplied timezone, but L029 silently defaults an omitted or null timezone to UTC.

Low
Category
Excessive Agency
Confidence
96% confidence
Finding

The skill accepts coordinates without a timezone despite describing both as explicitly supplied inputs; the CLI also advertises timezone as optional at L148. Because the timezone controls the requested forecast and date validation, this fallback can produce a UTC-day briefing rather than the intended city's local-day briefing.

Content

No source excerpt is available for this finding.