Back to skill

Security audit

Wubble

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward guide for connecting to Wubble's audio MCP service and includes appropriate user-confirmation and secret-handling cautions.

Before installing, be aware that Wubble MCP actions can create media and may consume Wubble credits; only approve generation or uploads when you intend to send that content to Wubble. The artifact also instructs agents not to log or reveal tokens, signed URLs, private media, prompts, lyrics, transcripts, or voice data unless explicitly approved.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 46)May include surrounding context.

md
## Authentication

Use the client-provided OAuth flow for protected Wubble MCP tools. Do not ask
the user for Wubble API keys, OAuth tokens, or secrets when OAuth is available.

If the MCP client asks for the remote server URL, use: