Back to skill

Security audit

Google Drive Delete File

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it says, but it can trash Google Drive files without explicit confirmation or target-verification instructions.

Review this skill carefully before installing. It is not deceptive or self-installing, but an agent using it should only run it after you provide or confirm the exact Google Drive file ID and understand that the target may be moved to trash under the permissions of the configured `gog` account.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

This skill performs a destructive operation but does not warn that it moves files to trash, which may still disrupt workflows, remove shared resources, or enable malicious prompting to cause data loss. In a deletion-focused skill, the absence of a clear safety warning and confirmation requirement increases the chance that users or downstream agents invoke it without understanding the consequences.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The activation condition is overly broad: 'A file needs to be removed or moved to trash in Google Drive' does not require confirmation of file identity, ownership, scope, or user authorization before executing a destructive action. In an agentic context, this can cause unintended deletion from ambiguous prompts or weak task matching, making accidental or unauthorized trashing significantly more likely.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.