Back to skill

Security audit

YOUKU User Profile API

Security checks for vulnerabilities and agentic risk

Overview

This skill is narrowly focused on one YOUKU profile lookup, but it handles the JustOneAPI token in ways that can expose it through command arguments and URL query strings.

Review this skill before installing if the JustOneAPI token has broad permissions or billing impact. Use a scoped or short-lived token if available, avoid sharing logs or process telemetry that may contain command arguments or URLs, and rotate the token if it may already have been exposed.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
bin/run.mjs:166
Finding

API Token Exposed Through Process Arguments and URL Query Parameters

Content
View full analysis
"}' ``` The operation manifest defines the token as a query parameter: ```js { "defaultValue": null, "description": "TOKEN", "enumValues": [], "location": "query", "name": "token", "required": true, "schemaType": "string" } ``` The helper copies the command-line token into the request parameters: ```js function injectToken(operation, params, cliToken) { const tokenParam = operation.parameters.find((parameter) => parameter.name === "token"); if (!tokenParam || params.token !== undefined) { return; } if (!cliToken) { fail("--token is required for this operation.", { operationId: operation.operationId, }); } params.token = cliToken; } ``` All parameters marked as query parameters, including the token, are appended to the request URL: ```js function applyQueryParams(operation, params, url) { for (const parameter of operation.parameters.filter((item) => item.location === "query")) { const value = params[parameter.name]; if (value === undefined) { continue; } appendValue(url.searchParams, parameter.name, value); } } function appendValue(searchParams, name, value) { if (Array.isArray(value)) { for (const item of value) { appendValue(searchParams, name, item); } return; } if (value && typeof value === "object") { searchParams.append(name, JSON.stringify(value)); return; } searchParams.append(name, String(value)); } ``` The resulting UR ...[truncated 3635 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
91% confidence
Finding

The skill invokes a network-capable helper (node .../bin/run.mjs) that sends data to an external API, but the manifest does not declare an explicit tool scope such as permissions or allowed-tools. This creates a governance gap: hosts or reviewers may not be able to clearly enforce or audit that the skill performs network access, increasing the chance of unintended data egress or overly broad execution in permissive runtimes.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill sends the authentication token in the URL query string (token parameter), which is commonly exposed through logs, browser/history mechanisms, proxy caches, monitoring tools, and upstream server access logs. Even though the request uses HTTPS, query parameters are still more broadly observable than headers, so a leaked token could allow unauthorized use of the JustOneAPI account or associated data access.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The skill requires a token and a user identifier and sends both to an external third-party API, but the manifest provides no warning about credential handling, third-party data transfer, or privacy implications. In an agent context, this can lead to users or calling systems transmitting sensitive credentials and personal identifiers without informed consent or appropriate trust evaluation.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The documentation describes an endpoint that requires a token and returns user profile data, but it gives no guidance on protecting authentication credentials or handling returned profile information as potentially sensitive data. In an agent-skill context, missing security warnings can lead developers or downstream agents to log tokens, expose them in URLs, or process profile data without appropriate access controls or minimization.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

This is a manifest-style JSON file, so vague-trigger checks apply. The description and operation summary explain what the API does, but they do not provide any explicit activation phrases, constraints, or exclusion conditions, making invocation scope broad and underspecified.

Content

No source excerpt is available for this finding.