Back to skill

Security audit

Douyin (TikTok China) User Profile API

Security checks for vulnerabilities and agentic risk

Overview

This skill is a narrow Douyin profile API wrapper, but it passes an API token through command-line arguments and a URL query string, which creates avoidable credential exposure risk.

Install only if you are comfortable sending Douyin secUid values and your JustOneAPI token to JustOneAPI. Prefer a short-lived or low-scope token, avoid running this in shared shells or logged automation, and rotate the token if it may have appeared in process logs, command history, or URL 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:65
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; ...[truncated 3430 chars]
Remediation
View remediation
"}' ``` - Continue warning users not to paste token values into chats, screenshots, or logs. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (7)

Credential Access

High
Category
Privilege Escalation
Confidence
89% confidence
Finding

This finding is substantiated by the manifest declaring an access token parameter and the implementation automatically injecting and sending it as part of the request URL. While the code does not appear to exfiltrate the token to an attacker-controlled host, handling credentials this way materially increases the chance of credential exposure via operational logging and third-party infrastructure.

Content

Scanner excerpt · bin/run.mjs (reported line 20)May include surrounding context.

js
"parameters": [
        {
          "defaultValue": null,
          "description": "Access token for this API service.",
          "enumValues": [],
          "location": "query",
          "name": "token",

Credential Access

High
Category
Privilege Escalation
Confidence
97% confidence
Finding

The API token is defined as a required query parameter, which increases the chance it will be exposed in logs, browser history, monitoring systems, proxies, and referrer-like telemetry. If leaked, the token could be reused to access the third-party API service and potentially consume quota or access associated data.

Content

Scanner excerpt · generated/operations.json (reported line 15)May include surrounding context.

json
"parameters": [
        {
          "defaultValue": null,
          "description": "Access token for this API service.",
          "enumValues": [],
          "location": "query",
          "name": "token",

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · generated/operations.md (reported line 19)May include surrounding context.

md
| Name | In | Required | Type | Default | Description |
| --- | --- | --- | --- | --- | --- |
| `token` | `query` | yes | `string` | n/a | Access token for this API service. |
| `secUid` | `query` | yes | `string` | n/a | The unique user ID (sec_uid) on Douyin. |

### Request body

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding

The skill invokes a network-capable helper (node .../bin/run.mjs) to call an external API, but the manifest does not declare an explicit tool scope such as permissions or allowed-tools. This creates a policy gap where reviewers and runtime controls may not clearly understand or restrict the skill’s external network behavior, increasing the chance of unintended data egress or broader-than-expected API access.

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 API access token as a query parameter and later appends all query parameters directly into the request URL. Tokens in URLs are commonly exposed through logs, browser/history records, proxy caches, monitoring systems, and error telemetry, creating unnecessary credential leakage risk even when HTTPS is used.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill sends a user identifier (secUid) and an API credential to a third-party endpoint, but the definition provides no warning, consent language, or data-handling notice. This is dangerous because users or downstream agents may unknowingly transmit sensitive account-linked data and secrets to an external service outside the primary platform.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The skill description states it retrieves Douyin user profile data including follower counts, verification status, and bio details for research and analysis, but it does not include any warning about handling third-party profile data or privacy implications. For markdown files, user-facing descriptions should disclose behaviors that may affect privacy or data handling when the skill accesses or processes user-related information.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.