ClawHub
Back to skill

Security audit

Binance Query Address Info

Security checks for vulnerabilities and agentic risk

Overview

This skill transparently queries public wallet holdings through a Binance Web3 endpoint and does not show hidden persistence, credential access, or destructive behavior.

Installers should understand that wallet addresses and chain IDs entered into this skill are sent to Binance Web3 to retrieve public portfolio data. Avoid using it when you do not want a queried address associated with that external request.

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
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • 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
Findings (1)

Lp3

Medium
Category
MCP Least Privilege
Confidence
84% confidence
Finding
The skill documents network-capable behavior by invoking a CLI that queries external on-chain/address data, but it does not declare any explicit tool scope such as allowed tools or permissions. This creates a policy and containment gap: an agent runtime may permit broader-than-intended network access or make unsafe assumptions about what the skill is authorized to do, reducing reviewability and increasing the chance of misuse if the implementation changes or is replaced.

Static analysis

No suspicious patterns detected.