Blockchain Balance Checker

• Outcome: Review
• Latest audit: May 29, 2026, 9:27 PM
• Version:
  1.0.5

Overview

The skill appears to do a legitimate blockchain balance lookup, but it needs review because it can send addresses on broad triggers and can expose the Tokenview API key in URLs or error output.

Install only if you are comfortable with queried wallet addresses being sent to Tokenview. Use a low-privilege or disposable Tokenview API key, avoid ambiguous address-only prompts, and consider revising the skill to require explicit confirmation and redact apikey values from all errors and logs.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (2)

Vague Triggers

Medium

• Confidence: 87% confidence
• Finding: The trigger definition is broad enough that any conversation containing something that looks like a blockchain address may be interpreted as a balance query, even without clear user intent. This can cause unintended external API calls, surprising behavior, and leakage of user-provided addresses to a third-party service, which is a privacy and safety concern in an agent context.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The API key is embedded in the query string, which can be exposed through proxy logs, browser/history equivalents, APM tooling, crash reports, or server-side access logs even when HTTPS is used. In a reusable agent skill context, this increases the chance of credential leakage across observability and debugging layers outside the developer's control.

VirusTotal

67/67 vendors flagged this skill as clean.