ClawHub
Back to skill

Security audit

Google Calendar Create Event

Security checks for vulnerabilities and agentic risk

Overview

This skill does one disclosed thing: create Google Calendar events through the gog CLI.

Install this only if you want the agent to create events in the Google Calendar account available to gog. Confirm the calendar, title, start and end time, and any other event details before allowing the command to run.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
90% confidence
Finding

The skill creates data in an external Google Calendar account but does not warn that using it will modify third-party hosted data. This omission increases the chance of unintended writes, privacy issues, or surprise side effects, especially in agentic workflows where users may not realize an external system will be changed.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The activation condition is extremely broad: any situation where a new event 'needs to be scheduled or created' triggers execution of the calendar-creation CLI. Without scope checks such as user confirmation, target calendar restrictions, or validation of event details, an agent could create external-service data based on ambiguous, indirect, or adversarial prompts.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.