Back to skill

Security audit

gina

Security checks for vulnerabilities and agentic risk

Overview

Gina is a simple scheduling-assistant skill with placeholder shell scripts and no evidence of hidden data access, persistence, exfiltration, or destructive behavior.

This skill appears safe to install as a lightweight assistant namespace. Before granting access to real calendars, reminders, or preferences in a future version, confirm that actions require clear user intent and that calendar mutations ask for confirmation.

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)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill instructs users to invoke it 'by name' and says it responds to natural language and schedule context, which creates a broad activation surface. In a voice or chat environment, ambiguous name-based triggering can cause unintended invocation, cross-skill confusion, or unauthorized access to scheduling functions when ordinary conversation happens to match the trigger.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The example 'Morning brief, please' omits the documented named invocation, making the activation rules inconsistent. This increases the chance that generic phrases will trigger the skill unexpectedly or that routing logic will interpret unrelated user speech as a request for Gina, especially in environments with multiple assistants or overlapping intents.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.