ClawHub

ERCData

Security checks across malware telemetry and agentic risk

Overview

ERCData is a purpose-aligned blockchain skill, but users should treat its write commands as real Base mainnet transactions and avoid putting raw secrets on-chain.

Install only if you are comfortable giving the skill a wallet key for Base transactions. Use a dedicated, minimally funded wallet, verify the contract and RPC endpoint before writes, manually approve store/verify/access/snapshot actions, and store hashes or client-side encrypted data rather than raw secrets.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Description-Behavior Mismatch

Medium
Confidence
95% confidence
Finding
The CLI usage text advertises a `store-encrypted` command and private/encrypted storage capabilities that are not actually implemented in the parser or command dispatch. In a blockchain data-storage tool, this can mislead users into believing sensitive data will be encrypted or privately protected when the code only stores raw bytes and relies on contract-side privacy semantics, increasing the risk of accidental on-chain disclosure.

Intent-Code Divergence

Medium
Confidence
73% confidence
Finding
The `info` command is presented as 'public only' but directly calls `getData`, which may return metadata about private entries and depends entirely on contract-side enforcement. In this skill context, users may trust the CLI label and use it in workflows handling supposedly private AI data, causing unintended exposure of entry attributes or contents if the contract does not strictly restrict reads.

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The quick-start examples encourage immediate use of write operations without clearly warning that they create irreversible blockchain transactions and consume gas. In a blockchain skill that accepts a private key and can mutate on-chain state, missing upfront warnings materially increases the chance of accidental fund expenditure, unintended permanent publication of data, and irreversible state changes.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal