T07 · Tool Hijacking and Spoofing
- Location
energy.py:41- Finding
Synthetic Appliance Data Is Presented as Real Household Telemetry
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is framed as a passive local energy dashboard, but it presents simulated appliance data as household facts and steers agents toward appliance power-control workflows outside that passive scope.
Review before installing. Treat this as a demo/local visualization skill unless it clearly labels measured inputs and data provenance. Do not let it configure or trigger smart-plug, HVAC, breaker, or other appliance-control automations based on its current output. Run it only in an isolated environment with pinned dependencies and a private output directory.
energy.py:41Synthetic Appliance Data Is Presented as Real Household Telemetry
S2-MEMZERO-PROTOCOL.md:13Passive Monitoring Instructions Steer the Agent Toward Physical Device Control
SKILL.md:9Third-Party Dependencies Are Installed Without Version or Integrity Pinning
energy.py:38Predictable Dashboard Filenames Permit Symlink-Based File Overwrite
The description is partially aligned: the code does local energy-style visualization, creates bar and trend charts, saves them locally, and does not use cloud analytics. However, there is a material description/behavior gap in the supplied chunk. The dashboard is built from hardcoded sample data and simulated 30-day consumption rather than actual spatial inventory data. Also, the description explicitly mentions Bar/Pie/Trend dashboards, but the shown implementation only produces bar and line/trend outputs, with no pie chart generation. Finally, inventory mapping and breaker-reading are declared as part of the skill’s purpose, but their implementations are omitted from the supplied chunk, so the actual demonstrated behavior is narrower than advertised. This is best classified as a mismatch because the represented capability suggests real local inventory-driven analytics, while the visible code mainly produces synthetic local visualizations.
The skill uses 'env' capability that is not listed in its permissions. This may indicate deceptive intent or missing permission declarations.
The documentation says the skill is only a passive scanner/chart generator, but the example explicitly directs the agent to convert outputs into operational recommendations and to invoke other skills for power-cutting automations. This creates a scope-expansion hazard: downstream agents may treat descriptive telemetry as authorization for control actions, increasing the chance of unsafe or unintended actuation.
The example pushes the agent beyond local visualization into proactive inference, behavioral interpretation, and home automation orchestration. That broadening is dangerous because an agent may over-trust the example as policy, make unsupported assumptions from energy charts, and trigger actions in other systems without explicit user intent or verified safety conditions.
The example response is written entirely in Chinese and addresses the user as '主人', with no indication that language choice is user-selectable or context-dependent. Under the policy criteria, forcing a specific language or locale without user opt-in is a natural-language policy violation unless clearly documented and justified.
The markdown recommends automatic power-cutting of appliances and standby loads without warning about risks such as interrupting climate control, corrupting devices, disabling safety-critical equipment, or affecting user comfort and availability. In a home-automation context, presenting shutoff automation as a routine optimization can lead to real-world physical and operational consequences if copied by an agent or user without safeguards.
The document explicitly assigns an 'Active Control Agent' the ability to cut power or adjust device state, but it provides no requirement for explicit user confirmation, authorization boundaries, safety interlocks, or warnings about system-impacting actions. In an energy-management skill, this materially increases risk because users may assume the feature is observational only, while the protocol enables actuator behavior that could disrupt appliances, safety devices, or critical household operations.
The skill instructs the agent to run local Python commands and generate local image files, but does not require a user-facing warning or confirmation before doing so. This is dangerous because users may not realize the agent is invoking local execution, creating files, and potentially exposing local file URIs in the response.
The skill says to generate dashboards whenever the user asks for an energy report, which is a broad natural-language trigger that could cause command execution in response to common phrasing without sufficiently explicit user consent. In an agentic context, overly broad invocation rules increase the chance of unintended local execution and file generation.
The file states 'You MUST present these image links directly to the user in your markdown response,' which mandates a specific presentation format regardless of user preference. This is a natural-language policy concern because it imposes an output mode without offering choice or documenting a justified requirement.
The banner line presents the skill description bilingually, which indicates a language preference is embedded in the skill. Under the policy rule, forcing or assuming a specific language/locale without user opt-in can be a natural-language policy issue, and no user choice or justification is visible in this file.
The skill returns a user-facing natural-language string in both English and Chinese regardless of any user preference. This is a locale/language policy concern because the file does not provide a language selection mechanism or explain why a fixed bilingual response is required.