Security audit

Douyin Creator Marketplace (Xingtu) Creator Visibility Status API

Security checks for vulnerabilities and agentic risk

Overview

The skill is a focused API wrapper, but it places the JustOneAPI token in the request URL where it may be exposed in logs.

Review this before installing if the token has meaningful account, quota, billing, or data access. Use a narrowly scoped or short-lived JustOneAPI token if possible, avoid logging full request URLs, and rotate the token if it may already have appeared in shell history, process telemetry, proxy logs, or API logs.

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:25
Finding: Reusable API Token Exposed in URL Query String
Content: View full analysis
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)); } ``` ### Technical Analysis The helper stores the reusable JustOneAPI authentication token in `params.token`. Because the manifest declares this field as having the `query` location, `applyQueryParams()` appends the credential to the URL before the request is sent. Al ...[truncated 2997 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: 98% confidence
Finding: The skill defines the authentication token as a query parameter and injects it into the request URL, which causes the secret to be placed in the full URL. Query-string tokens are commonly exposed through logs, browser/history artifacts, proxy and CDN telemetry, monitoring systems, and error reporting, making accidental credential disclosure more likely even when HTTPS is used. In this skill context, the risk is real because the code is a generic API wrapper and provides no warning to users that their token will travel in the URL.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 96% confidence
Finding: Passing an authentication token in the query string is risky because query parameters are commonly logged by servers, proxies, observability tools, browser histories, and intermediary infrastructure. This increases the chance of credential leakage and replay, especially since the manifest does not warn users or indicate compensating controls.
Content: No source excerpt is available for this finding.

Vague Triggers

Low

Category: Not specified by scanner
Confidence: 90% confidence
Finding: This is a manifest-style JSON file, so vague-trigger checks apply. The file provides a general description of what the skill does but does not define any explicit activation phrases, scope limitations, or exclusion conditions, which can make invocation criteria ambiguous in systems that infer triggers from metadata.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 87% confidence
Finding: The operation documentation describes access to creator visibility, discovery eligibility, and campaign display signals but does not clearly warn that the endpoint requires a user authentication token and exposes potentially sensitive account evaluation data. This omission can cause downstream agents or users to invoke the API without appropriate consent, privacy review, or token-handling precautions, increasing the risk of misuse or overcollection.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.