ClawHub
Back to skill

Security audit

X5 Protocol Client

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed X5 API client that reads user-selected request files or parameters and sends requests to user-specified endpoints, with no hidden persistence or unrelated behavior found.

Install only if you need to create or test X5 protocol requests. Treat .x5 files like API instructions: review the URL, headers, body, and app credentials before sending, prefer HTTPS outside localhost, and avoid putting long-lived secrets in shared terminals, logs, dry-run output, or generated cURL commands.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Lp3

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding
The skill clearly instructs the agent to read local files, invoke a Python script, and send network requests, yet it declares no permissions or user-facing warning about those capabilities. In an agent setting, undeclared file, shell, and network actions reduce transparency and can lead to unexpected exfiltration of local request files, credentials, or payloads to remote endpoints.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
This skill is designed to handle appid/appkey credentials and arbitrary request bodies, then send them to remote URLs, but the documentation does not warn that sensitive secrets and payload data may be transmitted externally. In practice, users may paste production credentials or private data into commands without understanding that the skill will package and send them to the specified endpoint.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The dry-run mode is documented as showing the signature, Base64 payload, and full envelope, but there is no warning that these outputs can expose app identifiers, signed request contents, and potentially secrets in shells, logs, transcripts, or shared terminals. Even without sending a request, revealing the fully encoded request material can leak sensitive operational data.

Missing User Warnings

Medium
Confidence
76% confidence
Finding
The CLI transmits encoded request data, potentially including sensitive business payloads and authentication-derived material, immediately when invoked, without an explicit confirmation or prominent warning. In a terminal tool that accepts .x5 files and inline credentials, this increases the chance of accidental disclosure to unintended endpoints, especially when users run unfamiliar request files.

Static analysis

No suspicious patterns detected.