ClawHub
Back to skill

Security audit

Ticketmaster

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a Ticketmaster connector, but it is advertised as read/search only while also exposing an untagged Season Ticketing command that may change account state.

Review this skill before installing. It may be fine for Ticketmaster lookups, but do not allow it to run Season Ticketing commands unless you understand the exact payload and effect and have explicitly approved the action. The publisher should mark write-capable actions clearly or separate read-only Ticketmaster search from account-changing operations.

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Description-Behavior Mismatch

High
Confidence
98% confidence
Finding
The manifest and description frame the skill as only for 'searching and reading data,' but the documented actions include `execute_season_ticketing_command`, which can change Ticketmaster state. This mismatch is dangerous because agents or users may rely on the read-only description and invoke the skill in contexts where write-capable tools should be excluded or require stronger confirmation.

Intent-Code Divergence

Medium
Confidence
96% confidence
Finding
The documentation promises that state-changing actions will be tagged `[write]` or `[destructive]`, but the listed command execution action is untagged. That inconsistency can cause an agent to treat a mutating operation as a safe read and execute it without the explicit confirmation the skill itself says is required.

Vague Triggers

Medium
Confidence
90% confidence
Finding
The instruction to use this skill for 'ANY Ticketmaster request' is overly broad and encourages routing all Ticketmaster-related tasks through a skill that is not actually limited to read-only behavior. In context, this broad scope increases the chance that sensitive or state-changing tasks are handled by default without appropriate risk-based selection or restrictions.

Static analysis

No suspicious patterns detected.