ClawHub
Back to skill

Security audit

Dca Signal

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent paid crypto signal integration, but it gives an agent automatic wallet-based payment authority without strong user confirmation or spend-limit guidance.

Install only if you are comfortable letting agent workflows use an EVM private key for paid x402 requests. Prefer a dedicated low-balance wallet, verify Base USDC funding and per-call pricing, and gate each invocation so loops or repeated DCA checks cannot create unintended charges.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The skill instructs the agent to make an x402-authenticated request using an EVM private key and notes that payment authorization happens automatically, but it does not clearly warn that each invocation can spend funds from the configured wallet. In an agent setting, this can lead to unintended paid calls, repeated micro-charges, or abuse through automated invocation because the skill is framed as a normal data-fetching step rather than a spend-authorizing action.

Static analysis

No suspicious patterns detected.