Back to skill

Security audit

Weibo User Fans API

Security checks for vulnerabilities and agentic risk

Overview

This is a narrow JustOneAPI wrapper for one Weibo fans lookup endpoint, with a real but disclosed credential-handling risk around the API token.

Install only if you are comfortable sending your JustOneAPI token and the target Weibo UID to api.justoneapi.com. Prefer a narrowly scoped or disposable API token if available, avoid pasting token values into chat or logs, and rotate the token if you suspect command-line 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:228
Finding

API Token Exposed Through Process 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 // bin/run.mjs:228-249 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 a ...[truncated 3183 chars]
Remediation
View remediation
"}' ``` 5. If the upstream API only supports query-string authentication: - Document this security limitation explicitly. - Use short-lived, narrowly scoped tokens where supported. - Configure gateways, proxies, servers, and observability systems to redact the `token` query parameter. - Ensure errors and diagnostics never include the complete request URL. - Rotate the token immediately if it may have appeared in logs. - Consider constructing the authenticated request as late as possible and clearing unnecessary in-memory references after use. 6. Reject a `token` property supplied through `--params-json` so callers cannot bypass the safer credential path after authentication is moved to an HTTP header. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • 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
Findings (7)

Credential Access

High
Category
Privilege Escalation
Confidence
98% confidence
Finding

The skill requires an API access token as a query parameter, which is a risky credential-handling pattern because query strings are commonly logged by clients, proxies, gateways, and servers. If exposed, the token could be reused to access the external API or associated account resources, making credential leakage more likely than if the token were sent in an Authorization header or dedicated secret channel.

Content

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

json
"parameters": [
        {
          "defaultValue": null,
          "description": "API access token.",
          "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 · bin/run.mjs (reported line 20)May include surrounding context.

js
| Name | In | Required | Type | Default | Description |
| --- | --- | --- | --- | --- | --- |
| `token` | `query` | yes | `string` | n/a | API access token. |
| `uid` | `query` | yes | `string` | n/a | Weibo User ID (UID). |
| `page` | `query` | no | `integer` | `1` | Page number, starting with 1. |

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 | API access token. |
| `uid` | `query` | yes | `string` | n/a | Weibo User ID (UID). |
| `page` | `query` | no | `integer` | `1` | Page number, starting with 1. |

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding

The skill invokes a network-capable helper (node .../bin/run.mjs) and requires an API token, but it does not declare an explicit tool scope such as permissions or allowed-tools. This creates a trust-gap where reviewers and enforcement systems may not clearly see that the skill can make outbound requests, increasing the risk of unintended data exfiltration or over-broad execution in agents that rely on manifest-declared permissions.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill transmits the API access token in the URL query string, which is commonly exposed through logs, browser/history equivalents, proxy infrastructure, monitoring tools, and upstream error reporting. Even though the request is sent over HTTPS, query parameters are more widely propagated than headers, so placing credentials there unnecessarily increases the chance of credential leakage.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The manifest does not warn users that it sends both an API token and a user identifier to a third-party external service. This weakens informed consent and can lead to unintended disclosure of credentials and target identifiers, especially in agent workflows where users may not realize outbound transmission occurs.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

This JSON file is a manifest-type file, so vague-trigger checks apply. The description explains what API call the skill makes, but it does not define any explicit invocation conditions, trigger phrases, scope limits, or exclusion conditions, which can make activation boundaries unclear in systems that infer routing from manifest text.

Content

No source excerpt is available for this finding.