ClawHub
Back to skill

Security audit

Regime Confluence

Security checks for vulnerabilities and agentic risk

Overview

This paid trading-signal skill is coherent, but it asks an agent to use a wallet private key for automatic per-call payments without enough consent or key-safety boundaries.

Review before installing. Use only a dedicated wallet with minimal USDC, never a primary wallet private key, and require explicit approval or a strict spending limit for each paid signal call. Treat the output as trading information, not financial advice.

SkillSpector

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

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill documentation instructs the agent to supply an EVM private key directly to a third-party paid request flow, but it does not prominently warn that this credential authorizes wallet-backed spending and must be handled as highly sensitive secret material. In an agent setting, this can normalize unsafe key exposure or cause users to connect a funded wallet for automated micropayments without clear consent boundaries, increasing the risk of unintended charges or key compromise if the surrounding runtime is not hardened.

Static analysis

No suspicious patterns detected.