ClawHub
Back to skill

Security audit

crypto-signals-router

Security checks for vulnerabilities and agentic risk

Overview

The skill is transparent about being a 24/7 crypto-signals automation router, but it routes into scheduled wallet spending and Telegram publishing with long-lived secrets and limited per-action user control.

Review this carefully before installing. Only use it with a low-balance wallet, strict spend caps, a dedicated Telegram bot/channel, locked-down .env file permissions, and a clear way to disable the scheduled jobs. Do not point it at a primary wallet or production channel unless you have inspected the referenced scripts and understand every automated action.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Medium
Confidence
89% confidence
Finding
The router is configured to trigger on a very broad set of crypto-related prompts and explicitly says to 'lean toward delegation,' which increases the chance of invoking downstream agents that can spend funds, publish to Telegram, or run scheduled operations without sufficiently narrow user intent. In this skill’s context, overbroad routing is more dangerous because the mapped agents are tied to wallet actions, automated publishing, and orchestration scripts rather than read-only analysis.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill describes always-on operation, scheduled cycles, watchdog behavior, Telegram publishing, and x402 wallet spending, but it does not prominently warn users that invoking or installing it may enable automated external actions and recurring financial activity. This omission materially increases risk because users may treat the router as a simple analysis assistant when it can lead to persistent automation with real-world side effects.

Credential Access

High
Category
Privilege Escalation
Content
bash ~/.gemini/config/plugins/crypto-signals-plugin/scripts/install.sh

# 2. Fill in your credentials
nano ~/.gemini/config/plugins/crypto-signals-plugin/.env

# 3. Test the first cycle manually
bash ~/.gemini/config/plugins/crypto-signals-plugin/scripts/run-cycle.sh
Confidence
78% confidence
Finding
The quick-start explicitly tells the operator to open and populate a .env file containing highly sensitive secrets, including a wallet private key and Telegram bot token. In the context of an always-on automation skill with scheduled spending and publishing, centralizing long-lived credentials in a plaintext .env materially raises the risk of credential theft, accidental disclosure, or misuse by downstream scripts.

Static analysis

No suspicious patterns detected.