ClawHub
Back to skill

Security audit

UAPI 查询 MC 服务器 接口

Security checks for vulnerabilities and agentic risk

Overview

This skill is a simple, disclosed Minecraft server-status API guide with some overbroad trigger wording but no hidden execution, persistence, or sensitive local access.

Installers should understand that this skill sends Minecraft server addresses to uapis.cn when used. The publisher should narrow the trigger keywords to server-status requests only and ideally state that responses should follow the user's language preference.

A.I.G

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (3)

Vague Triggers

Medium
Confidence
94% confidence
Finding
The trigger list includes broad English terms such as "serverstatus," "minecraft player lookup," and "minecraft name history," which do not cleanly map to this single endpoint. This can cause the agent to select the wrong skill for unrelated requests, leading to incorrect API calls, misrouted user data, or failure to apply the right validation and consent flow for the actual task.

Natural-Language Policy Violations

Medium
Confidence
89% confidence
Finding
The document is primarily written in Chinese and presents the skill guidance in that language without stating that users may choose another language. Under the policy, forcing a specific language without opt-in is a natural-language policy violation unless a justified locale constraint is documented.

Natural-Language Policy Violations

Low
Confidence
78% confidence
Finding
The file prominently describes the skill in Chinese and provides Chinese-first invocation guidance, but does not state that responses should follow the user's preferred language or offer a language choice. This can be a language/locale policy concern when a skill may be used by users who did not opt into Chinese output.

Static analysis

No suspicious patterns detected.