ClawHub
Back to skill

Security audit

xinjianxue-skill-manage_up-global

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed paid API integration that asks for sensitive personal details and service credentials, but its behavior is coherent with its stated XinJianXue advisory purpose.

Install only if you are comfortable sending birth details, gender, and location information to XinJianXue and letting the assistant use a one-time authorization code to bind to your account. Confirm the domain yourself, avoid sharing the code anywhere else, and use dedicated credential storage for the generated license and API key.

A.I.G

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
SKILL.md:74
Finding

Excessive Personal Data Collection and Unsafe API Credential Transport

Content
View full analysis
", "birth": "1990-01-01 08:30", "gender": "Female", "country": "United States", "place": "New York City", "current_country": "United States", "current_place": "New York City" } ``` ### Technical Analysis The Skill directs the agent to collect and transmit date and time of birth, gender, birthplace, and current location to an external service. These identity-linked attributes are broader than the information ordinarily required to provide workplace communication or manager-relationship advice. Combining these attributes can enable profiling and identity correlation. The report endpoint also requires the `api_key` to be placed in the JSON request body. Request bodies are commonly captured by application diagnostics, HTTP tracing, reverse-proxy logs, observability platforms, and debugging tools. Authentication secrets in bodies are therefore more likely to be retained or disclosed than credentials carried exclusively in protected authorization headers. The onboarding workflow additionally requires the user to send a sensitive one-time authorization code through the c ...[truncated 2185 chars]
Remediation
View remediation

SkillSpector

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

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 112)May include surrounding context.

md
Call `POST /api/xinjianxue/ai/license/verify` (include credentials if you have them; body or headers are both accepted). **The only criterion is `pass`:**

- `pass: true` → **already onboarded**: use the APIs directly, and do not ask the user for any credential.
- No credentials / `pass: false` → act on the returned `msg`; **go to Step 1 only once you have confirmed "never onboarded"**. Do not blindly re-apply (re-applying produces an extra license that nobody uses).

### Step 1: Apply for the AI business license (once only)

Static analysis

No suspicious patterns detected.