Kuaishou User Profile API

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 7:29 AM UTC
• Version: 1.0.0

Overview

This is a focused Kuaishou profile lookup skill with disclosed network and token use, though its token handling deserves care.

Install only if you intend to call JustOneAPI for Kuaishou profile lookups. Use a scoped token if available, avoid exposing command lines or full request URLs in logs, rotate the token if it may have been logged, and treat returned creator profile data as potentially sensitive.

A.I.G

Vulnerability Patterns

• Insecure Skill Coding Practices: Finds exploitable flaws such as hardcoded secrets or command injection
• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally

Findings (1)

T09 · Insecure Skill Coding Practices

Warning

• Location: bin/run.mjs:72

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; } ``` ```js const url = new URL(operation.path, ensureBaseUrl(baseUrl)); applyPathParams(operation, params, url); applyQueryParams(operation, params, 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); } } ``` The documented invocation also passes the credential as a command-line argument: ```bash node {baseDir}/bin/run.mjs --operation "getUserProfileV1" --token "$JUST_ONE_API_TOKEN" --params-json '{"userId":""}' ``` ### Technical Analysis The helper places the JustOneAPI access token in two potentially observable locations: 1. The `--token` command-line argument may be visible through local process inspection, diagnostic tooling, shell tracing, process accounting, job runners, or command logging. 2. Be ...[truncated 2208 chars]

Remediation

View remediation

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands

Findings (8)

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 · 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 requires an access token as a query parameter, which is risky because query strings are commonly logged by servers, proxies, observability tools, browser history, and intermediary infrastructure. This increases the chance of credential exposure and unauthorized reuse of the token to access the third-party API service.

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: 95% confidence

Finding

The API requires an access token in a query parameter, which is a dangerous credential-handling pattern because query strings are commonly logged by servers, proxies, browser history, observability tools, and intermediary infrastructure. If the token is exposed, an attacker could reuse it to call the API and access protected Kuaishou profile data.

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. |
| `userId` | `query` | yes | `string` | n/a | The unique user ID on Kuaishou. |

### Request body

Undeclared Tool Scope

Medium

• Category: MCP Least Privilege
• Confidence: 90% confidence

Finding

The skill invokes a Node helper that performs outbound API requests using a bearer token, but the manifest does not declare an explicit tool scope such as allowed network access or permissions. This creates a transparency and governance gap: reviewers and runtime policy systems cannot easily constrain or audit the skill's network behavior, increasing the risk of unintended external data exfiltration or unauthorized API use.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 89% confidence

Finding

This code performs an outbound HTTP request using query parameters that include a service access token and a Kuaishou user ID, which are transmitted to an external API. While the manifest describes the API function, there is no confirmation prompt, user-facing log/print, or warning comment/docstring in this code disclosing that sensitive identifiers and credentials are sent over the network.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 88% confidence

Finding

The operation explicitly retrieves Kuaishou user profile data, including audience metrics and verification-related fields, and requires an access token, but the skill description provides no warning about handling sensitive profile data or credentialed access. This can mislead downstream users or agents into treating the API as low-risk, increasing the chance of inappropriate collection, sharing, or logging of personal or business-sensitive creator information.

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 what the skill does but does not specify when it should or should not be invoked, nor does it provide any limiting context or exclusion examples. For manifest files, the absence of specific trigger scope can make activation criteria overly broad or ambiguous.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

• Category: Not specified by scanner
• Confidence: 63% confidence

Finding

The natural-language descriptions and tags constrain the skill to Kuaishou-specific usage, but the file provides no user-facing explanation of that platform-specific limitation or any opt-in/choice language. This can create a locale/platform policy concern when a skill implicitly forces one platform context without documented justification.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.