Back to skill

Security audit

Cloud File Hydration Nudge

Security checks for vulnerabilities and agentic risk

Overview

This skill gives cautious instructions for hydrating unreadable cloud placeholder files and repeatedly emphasizes verification, narrow permissions, and user consent for sync-state changes.

Before installing, be aware that the skill may guide an agent to inspect cloud-file provider state and use approved local automation to trigger downloads for specific unreadable files. This is disclosed and constrained, but only grant Accessibility or similar permissions to a trusted narrow helper, not a broad runtime, and keep manual control over provider sync state.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 182)May include surrounding context.

md
- Folder cloud-button hydration can work recursively, including nested child files, but a helper must poll every target child with bounded reads until success or timeout.
- A folder may report `isDownloaded = 1` while `isRecursivelyDownloaded = 0`; do not treat folder `isDownloaded` as proof that child bytes are available.
- Temporary FSEvents observation saw events during offload and hydration, suggesting event-driven intake is plausible. Automator Folder Action testing separately showed `adding folder items` did not fire for offload/hydration of an existing file.
- Paused/offline/quit sync should be treated as a user-controlled state. Do not start, resume, or unpause OneDrive without consent.

### OneDrive Paths That Are Not Proof Of Hydration