Ticketmaster

Security checks across malware telemetry and agentic risk

Overview

This Ticketmaster skill is mostly coherent, but it needs review because it combines broad Ticketmaster auto-routing with an under-scoped Season Ticketing command execution action.

Install only if you intend agents to use your OOMOL-connected Ticketmaster account. Treat read/search/detail actions as normal connector use, but require explicit user confirmation before running execute_season_ticketing_command or any payload that could change season ticketing/account state. The skill author should narrow the trigger wording and document the exact scope and effects of the Season Ticketing command action.

SkillSpector

By NVIDIA

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 (1)

Vague Triggers

Medium

Confidence: 93% confidence
Finding: The trigger text says to use this skill for ANY Ticketmaster request and instead of calling the API directly, which is overly broad and can cause the agent to invoke the skill whenever Ticketmaster is merely mentioned rather than when it is actually the correct tool. Over-broad routing increases the chance of unintended connector execution, unnecessary external data access, and incorrect handling of user intent.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal