Weibo User Followers API

• Outcome: Review
• Latest audit: May 29, 2026, 9:38 PM
• Version:
  1.0.0

Overview

This skill appears to do its stated Weibo follower lookup, but it handles the API token in ways that can expose it in command arguments and request URLs.

Install only if you are comfortable sending your JustOneAPI token and requested Weibo UID to JustOneAPI. Prefer a version that reads the token directly from the environment and sends it in an Authorization header or other non-URL mechanism; use a scoped, rotatable token and avoid running the documented command on shared or heavily logged systems.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (3)

Missing User Warnings

Medium

• Confidence: 97% confidence
• Finding: The skill defines the API token as a query parameter and then appends all query parameters directly into the request URL. Query-string credentials are commonly exposed through logs, browser/history tooling, proxy infrastructure, monitoring systems, and error reporting, making accidental credential disclosure more likely even when HTTPS is used.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The skill requires an API access token but provides no user-facing warning about how the credential is handled, transmitted, or protected. Because the token is passed as a query parameter, it may be exposed in logs, browser histories, proxies, analytics systems, or other intermediary telemetry, increasing risk of credential leakage.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The documentation instructs callers to send an API access token in the query string, which is commonly exposed through browser history, intermediary logs, reverse proxies, analytics tooling, and referrer headers. Even in a simple API skill, this increases the chance of credential leakage compared with sending the token in an authorization header or other protected channel.

VirusTotal

62/62 vendors flagged this skill as clean.