Security audit

Douyin Creator Marketplace (Xingtu) Follower Growth Trend API

Security checks for vulnerabilities and agentic risk

Overview

The skill is a focused API wrapper, but it exposes the user's API token through command-line arguments and URL query parameters.

Install only if you accept that the JustOneAPI token may appear in process metadata and request URLs. Prefer a version that reads the token directly from the environment and sends it in an Authorization header; if you use this version, keep the token short-lived and rotate it if logs may have captured full URLs or command lines.

A.I.G

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:27
Finding: API Credential 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 directly to the 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") { ...[truncated 3239 chars]
Remediation: View remediation

SkillSpector

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: 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: 96% confidence
Finding: The skill requires the authentication token to be sent as a query parameter, which exposes the secret in URLs. Query strings are commonly logged by client tools, proxies, web servers, browser history, shell history, and monitoring systems, increasing the chance of credential leakage even though the request uses HTTPS.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 98% confidence
Finding: Passing an authentication token in the query string is dangerous because query parameters are commonly logged by servers, proxies, browser history, analytics systems, and debugging tools. Even over HTTPS, the token may be exposed through operational logs or accidental sharing, enabling unauthorized API access if the token is reused or long-lived.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The documentation explicitly instructs clients to send a user authentication token in the URL query string. Query parameters are commonly logged by browsers, proxies, web servers, API gateways, monitoring tools, and Referer headers, which can expose the token to unintended parties and enable unauthorized API access.
Content: No source excerpt is available for this finding.

Vague Triggers

Low

Category: Not specified by scanner
Confidence: 84% confidence
Finding: This manifest-style JSON describes the skill’s function in general terms but does not define any explicit trigger phrases, activation boundaries, or negative examples. For manifest files, the absence of clear trigger scope can make invocation matching ambiguous and increase the chance of unintended activation.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.