ClawHub
Back to skill

Security audit

节点

Security checks for vulnerabilities and agentic risk

Overview

This Dogecoin node skill is purpose-aligned but needs review because it asks for command and file authority while giving vague operating boundaries and unsupported safety claims.

Install only if you are comfortable with an agent helping run system commands and modify files for Dogecoin node setup. Before use, require the agent to show each command, file change, RPC configuration, exposed port, and service start or stop action for your approval.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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)

Intent-Code Divergence

Medium
Confidence
94% confidence
Finding
The skill claims that only whitelisted commands are executed, but the document contains no actual whitelist, validation rules, or enforcement logic. In a skill with declared exec capability, this can mislead users and downstream agents into trusting command execution safety that is not actually implemented, increasing the risk of arbitrary or unsafe command execution.

Vague Triggers

Medium
Confidence
85% confidence
Finding
The activation/usage description is broad and ambiguous, telling the agent to use the skill whenever users need 'node-related' functionality without clearly bounding permitted actions. Because the skill has read, write, and exec tools, vague invocation criteria can cause overreach into system changes, network operations, or file modifications beyond what the user explicitly intended.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill advertises file handling, API integration, and command execution, but does not provide a prominent, explicit warning that using it may write files, run system commands, or contact external services. In the context of infrastructure/node setup, these side effects are materially significant and can alter host state or expose services if triggered without informed consent.

Static analysis

No suspicious patterns detected.