Back to skill

Security audit

YOUKU Video Details API

Security checks for vulnerabilities and agentic risk

Overview

This is a narrow YOUKU video-detail lookup skill that calls a declared JustOneAPI endpoint, with a credential-handling caveat users should understand.

Install only if you are comfortable using a JustOneAPI token for YOUKU video metadata lookups. Prefer a short-lived, scoped token if available, avoid sharing command logs or full request URLs, and rotate the token if it may have appeared in process listings or logs.

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:25
Finding

API Token Exposed Through Command-Line Arguments and URL Query Parameters

Content
View full analysis
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 query parameters, including the token, are appended to the URL before transmission: ```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); } } ``` The credential-bearing URL is sent to the remote service: ```js response = await fetch(url, requestInit); ``` The documented invocation also exposes the token through the process argument list: ```bash node {baseDir}/bin/run.mjs --operation "getYoukuVideoDetailV1" --token "$JUST_ONE_API_TOKEN" --params-json '{"videoId":""}' ``` ### Technical Analysis The API token follows this data flow: 1. The shell expands `JUST_ONE_API_TOKEN` into the `--token` command-line argument. 2. `pa ...[truncated 2342 chars]
Remediation
View remediation
"}' ``` Prefer configuring the environment outside the command itself when supported by the execution environment. 5. If JustOneAPI only supports query-based authentication, document that limitation, configure all intermediaries to redact the `token` parameter, disable full-URL logging where possible, and use short-lived, narrowly scoped tokens. 6. Ensure error reporting, telemetry, tracing, and debugging code never print authorization headers, environment variables, command-line arguments, or complete credential-bearing URLs. 7. Rotate any token that may already have appeared in process-monitoring records or request logs. ]]>
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 (3)

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

Requiring an authentication token in the query string is risky because query parameters are commonly logged by clients, proxies, gateways, observability tooling, browser history, and server access logs. Even over HTTPS, the token may be exposed through operational logging or accidental sharing, enabling unauthorized reuse of the credential.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

This manifest-style JSON describes the skill's purpose but provides no explicit activation boundaries, exclusion conditions, or examples of when it should not be invoked. For manifest files, this can make routing ambiguous because the skill is broadly described as fetching video details whenever a videoId is available.

Content

No source excerpt is available for this finding.