Back to skill

Security audit

Anticipation

Security checks for vulnerabilities and agentic risk

Overview

The skill is a simple Markdown-only anticipation aid, but it directs broad proactive inspection of private user context without clear consent or limits.

Install only if you are comfortable with an agent using broader session context to anticipate needs. It should be constrained to ask before reading browser state, open files, command/process information, or conversation history, and any learning should be session-scoped unless you explicitly approve persistent memory.

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

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:17
Finding
Unconsented Cross-Context Inspection at Session Start<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 17–22 **Vulnerability Type**: `T05: Unauthorized Access and Privilege Escalation` **Risk Level**: Medium ### Vulnerable Code ```text ## Bei Session-Start 1. Conversation Summaries → Wiederkehrende Themen? 2. Offene Dateien → Aktuelles Projekt? 3. Running Commands → Hängende Prozesse? 4. Browser-Tabs → Was sucht User? ``` ### Technical Analysis The skill instructs the agent to inspect conversation summaries, open files, running commands, and browser tabs automatically at the beginning of a session. These data sources can contain private communications, credentials, confidential source code, command arguments, browsing history, and information unrelated to the user's current request. The instruction does not establish: - An explicit user-consent requirement - A task-specific necessity check - An allowlist of permitted resources - Scope or sensitivity restrictions - Data-minimization and retention controls - A prohibition against disclosing discovered information The skill does not itself grant additional operating-system privileges. However, when used by an agent that already has tools capable of observing these resources, it encourages the agent to exercise that access beyond the least privilege needed for the current task. ### Attack Path 1. A user or platform loads the skill at the start of a session. 2. The skill directs the agent to inspect conversation summaries, open files, running commands, and browser tabs. 3. If the host exposes tools capable of accessing those resources, the agent gathers information without first obtaining resource-specific user consent. 4. Sensitive or unrelated information enters the agent's working context. 5. The collected information may influence later actions or be unintentionally disclosed in generated responses. This path depends on the host granting the agent access to the listed resources; the Markdown file contains no independent mechanism ...[truncated 646 chars]
Remediation
<![CDATA[ ## Remediation Suggestions 1. Remove automatic inspection of browser tabs, open files, running commands, and conversation history. 2. Require explicit, informed user consent before accessing each category of contextual data. 3. Limit access to resources directly identified by the user or demonstrably necessary for the active request. 4. Prefer metadata-only checks where possible, and do not read file, browser, or command contents unless required. 5. Apply allowlists for approved files, applications, processes, and conversation scopes. 6. Warn the user when requested context may contain credentials or other sensitive information. 7. Prevent contextual information from being stored in persistent memory unless the user explicitly requests it. 8. Add a rule prohibiting disclosure or reuse of observed information outside the current authorized task. 9. Ensure the host platform enforces tool-level permission prompts and least-privilege access independently of skill instructions. A safer instruction would be: ```text At session start, use only the context explicitly supplied for the current request. Before inspecting conversation history, files, commands, processes, or browser state, explain why access is necessary and obtain the user's explicit consent. Access only the minimum approved resource and do not persist discovered information. ``` ]]>
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)

Natural-Language Policy Violations

Medium
Confidence
90% confidence
Finding
The file is written entirely in German and the description/instructions imply the skill operates in that language by default, without offering a language choice or documenting a justified region-specific scope. This can violate language or locale policy when users have not opted into German-only interaction.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The skill explicitly instructs proactive inspection of privacy-sensitive context sources such as conversation summaries, open files, running commands, and browser tabs without any notice, consent boundary, or minimization rule. This creates a real privacy and data-exposure risk because the agent is directed to infer needs from user activity beyond the immediate request.

Ssd 3

Medium
Confidence
96% confidence
Finding
The skill encourages broad monitoring of browser tabs, running commands, files, and historical conversation context to predict user needs proactively. In skill context, this makes the issue more dangerous because the entire design centers on continuous behavioral inference, increasing the chance of overscoped surveillance, exposure of sensitive data, and actions based on information the user did not intentionally provide for the current task.

Ssd 3

Medium
Confidence
92% confidence
Finding
The directives to 'learn_pattern' and 'learn_from_mistake' imply retention of behavioral data across interactions without describing consent, minimization, deletion, or storage limits. Persistent profiling can accumulate sensitive preferences or work habits over time and can be misused or leaked even if the author's intent is product improvement.

Static analysis

No suspicious patterns detected.