ClawHub
Back to skill

Security audit

Avalanche Analytics AVAX生态分析

Security checks for vulnerabilities and agentic risk

Overview

The skill is mainly an Avalanche analytics helper, but it includes under-disclosed payment verification code that can send wallet/payment data to SkillPay and exposes a payment API key.

Review before installing or paying. Treat the analytics numbers as illustrative unless independently verified, and do not provide a wallet address unless you are comfortable with it being sent to SkillPay. The publisher should rotate the exposed API key and document the payment provider, data sent, retention, and opt-in behavior.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Description-Behavior Mismatch

Medium
Confidence
91% confidence
Finding
The file implements a paid-access gate and payment verification flow that is not part of the stated Avalanche analytics functionality. Hidden or undocumented monetization logic can mislead users and reviewers, and in practice can block access, create compliance issues, or conceal data-sharing and billing behavior that was not clearly declared in the skill context.

Context-Inappropriate Capability

Medium
Confidence
88% confidence
Finding
This skill is described as an Avalanche analytics tool, but the code adds a third-party payment-verification capability unrelated to analytics itself. That mismatch increases supply-chain and trust risk because users invoking analytics may unknowingly interact with an external billing service and have their wallet metadata transmitted off-platform.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The code sends the user's wallet address and a timestamp to an external API without any notice or consent mechanism in this file. Wallet addresses are sensitive identifiers in blockchain contexts, and transmitting them to a third party can enable user tracking, profiling, and linkage of activity across sessions or services.

Static analysis

No suspicious patterns detected.