ClawHub
Back to skill

Security audit

Xiaohongshu (RedNote) User Profile API

Security checks for vulnerabilities and agentic risk

Overview

This is a narrow Xiaohongshu profile API wrapper, but it handles the required API token in exposure-prone ways that users should review before installing.

Install only if you are comfortable sending Xiaohongshu userIds and your JustOneAPI token to api.justoneapi.com. Use a scoped or low-privilege token if available, avoid running it where command lines or full URLs are logged, monitor API usage, and rotate the token if it may have appeared in logs or screenshots.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The skill explicitly models the API access token as a query parameter and later appends all query parameters to the URL. Query-string secrets are commonly exposed through logs, browser history, proxy caches, monitoring systems, and error reports, making accidental credential disclosure much more likely than if the token were sent in an Authorization header. In this skill context, the danger is real because the code is a generic API wrapper and provides no warning or mitigation before transmitting the secret this way.

Credential Access

High
Category
Privilege Escalation
Content
"parameters": [
        {
          "defaultValue": null,
          "description": "Access token for this API service.",
          "enumValues": [],
          "location": "query",
          "name": "token",
Confidence
95% confidence
Finding
The API requires an access token to be passed as a query parameter, which is unsafe because query strings are commonly logged by clients, proxies, gateways, browser history, and monitoring systems. If exposed, the token can be replayed to access the third-party API service and potentially retrieve data or incur usage charges.

Credential Access

High
Category
Privilege Escalation
Content
"parameters": [
        {
          "defaultValue": null,
          "description": "Access token for this API service.",
          "enumValues": [],
          "location": "query",
          "name": "token",
Confidence
95% confidence
Finding
This second operation repeats the same pattern of placing an access token in the URL query string, creating credential leakage risk through logs, caches, analytics tools, and intermediary infrastructure. Because the skill is an API interface, consumers may automatically follow this pattern, propagating insecure credential handling across integrations.

Static analysis

Detected: suspicious.secret_argv_exposure

Instructions pass high-value credentials through process argv.

Critical
Code
suspicious.secret_argv_exposure
Location
SKILL.md:46