ClawHub
Back to skill

Security audit

Reliable Bitcoin Price Feed

Security checks across malware telemetry and agentic risk

Overview

This skill appears to do what it claims: stream live Bitcoin price data from Bitquery, with clear cautions about its API key and network use.

Install this only if you intend to use Bitquery for live Bitcoin price streaming. Use a sandbox or virtual environment, keep BITQUERY_API_KEY in a secure environment variable, avoid logging full WebSocket URLs, and rotate the key if it may have appeared in logs or command history.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Lp3

Medium
Category
MCP Least Privilege
Confidence
96% confidence
Finding
The skill clearly requires environment access and outbound network/WebSocket connectivity, yet no corresponding permissions are declared. This creates a transparency and consent problem: installers and execution environments may not surface that the skill can read secrets and initiate external connections, increasing the chance of unsafe deployment.

Vague Triggers

Medium
Confidence
84% confidence
Finding
The trigger language is very broad and forceful ('ALWAYS use this skill' for generic live/streaming crypto requests), which can cause the agent to invoke this networked skill in situations the user did not specifically intend. Because the skill depends on a secret and external network access, over-triggering increases exposure to unnecessary secret use, unintended outbound connections, and user confusion.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The WebSocket connection includes the Bitquery API key in the URL query string (`?token=...`). Even over WSS, query-string credentials are commonly exposed through client logs, proxy/load-balancer logs, monitoring tools, exception traces, and process inspection, making accidental credential disclosure more likely than if the token were sent in an authorization header or other safer channel. In this skill context, the risk is somewhat elevated because it is a reusable streaming tool intended for routine trader use, increasing the chance of operational logging and broad deployment.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.