Back to skill

Security audit

Douyin Creator Marketplace (Xingtu) Video Distribution API

Security checks for vulnerabilities and agentic risk

Overview

This skill is a focused JustOneAPI wrapper, with the main caution that its API token is passed on the command line and in the request query string.

Install only if you are comfortable sending the provided oAuthorId and your JustOneAPI token to JustOneAPI. Treat the token as sensitive, prefer short-lived or narrowly scoped tokens if available, avoid logging commands or full URLs, and rotate the token if you suspect process or URL logs captured it.

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:171
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; } function validateRequired(operation, params) { const missing = []; for (const parameter of operation.parameters) { if (parameter.required && params[parameter.name] === undefined) { missing.push(parameter.name); } } if (operation.requestBody?.required && params.body === undefined) { missing.push("body"); } ``` `bin/run.mjs:214-222`: ```javascript 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 manifest used by the executable defines the token as a query parameter: ```javascript { "defaultValue": null, "description": "User authentication token.", "enumValues": [], "location": "query", "name": "token", "required": true, "schemaType": "string" } ``` `SKILL.md:46` documents invocation through a command-line argument: ```bash node {baseDir}/bin/run.mjs --operation "gwApiDataSpAuthorVideoDistributionV1" --token "$JUST_ONE_API_TOKEN" --params-json '{"oAuthorId":""}' ``` ### Technical Analysis The API token is first supplied through the `--token` command-line argument and then inser ...[truncated 2821 chars]
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

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
98% confidence
Finding

The API authentication token is explicitly defined as a query parameter and later appended to the URL, which exposes it in logs, browser/history equivalents, proxy telemetry, and upstream monitoring systems. Even though HTTPS may protect it in transit, putting credentials in the URL materially increases accidental disclosure risk compared with using an Authorization header.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The file issues an outbound fetch request to a third-party API using a token and author ID, but it has no confirmation prompt, user-facing log, or comment/docstring disclosing that user or system data will be sent externally. For a code file, this matches the missing-warning criterion for network calls that transmit potentially sensitive data.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

The documentation explicitly requires a user authentication token but provides no guidance on secure handling, storage, redaction, or privacy considerations. In an agent skill context, this omission can lead integrators or downstream agents to place tokens in logs, prompts, URLs, or other insecure locations, increasing the chance of credential leakage.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.