ClawHub
Back to skill

Security audit

Zapper

Security checks across malware telemetry and agentic risk

Overview

This is a read-only Zapper API helper whose network use and API key storage are expected for its purpose, with privacy cautions around wallet lookups.

Install only if you are comfortable sending queried wallet addresses and portfolio-related requests to Zapper. Use a dedicated, revocable Zapper API key, keep the config file permissions restrictive, and never store seed phrases, private keys, or wallet credentials in this skill's config.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Lp3

Medium
Category
MCP Least Privilege
Confidence
84% confidence
Finding
The skill clearly instructs users to run shell commands and references shell scripts, but it does not declare corresponding permissions or capabilities. This weakens transparency and policy enforcement because a user or runtime may not realize the skill can invoke local shell tooling and make outbound network requests.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill sends wallet addresses and associated portfolio, NFT, and transaction-history queries to Zapper's external API, but the description does not clearly warn users that this data leaves the local environment. Wallet addresses are sensitive in context because they reveal holdings, activity, and cross-chain associations that can affect user privacy and profiling.

Missing User Warnings

Low
Confidence
90% confidence
Finding
The documentation instructs users to send wallet addresses and portfolio, NFT, and transaction-history queries to Zapper's third-party API but does not warn that this discloses potentially sensitive financial metadata to an external service. While wallet addresses are public on-chain, aggregating them with user intent and account analysis requests can create privacy and profiling risks, especially if users assume the skill is purely local.

Missing User Warnings

Medium
Confidence
84% confidence
Finding
The script sends wallet addresses and associated portfolio, NFT, and transaction queries to Zapper's third-party GraphQL API without any user-facing notice or consent mechanism. Wallet addresses and financial activity can be sensitive metadata, and transmitting them to an external service may create privacy and compliance risks for users who do not expect off-platform disclosure.

VirusTotal

63/63 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.