ClawHub
Back to skill

Security audit

Node Red Manager

Security checks for vulnerabilities and agentic risk

Overview

This skill is a Node-RED administration helper, but it enables high-impact changes with broad activation terms and little built-in safety guidance.

Install only if you intend to let the agent administer a specific Node-RED instance. Before use, narrow the trigger phrases, confirm the URL and Docker service are yours, protect the admin credentials, and require explicit approval before deploy, delete, restore, install, disable, remove, context changes, or Docker restarts.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Vague Triggers

High
Confidence
89% confidence
Finding
The trigger keywords are extremely broad (for example, 'node', 'red', 'manage', 'automate') and can cause this skill to activate in unrelated conversations. Because the skill exposes administrative and destructive operations over Node-RED, accidental invocation could lead to unauthorized flow changes, package installation/removal, or operational disruption.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The documentation advertises destructive and configuration-changing commands such as deploy, update-flow, delete-flow, restore, install-node, disable-node, and remove-node without requiring warnings, review steps, or confirmation. In an agent context with exec capability, this materially increases the risk of accidental or socially engineered modification of production automation workflows.

Missing User Warnings

Low
Confidence
80% confidence
Finding
The setup instructs users to place Node-RED admin credentials in environment variables but provides no privacy, storage, or handling guidance. In a tool with read/exec capabilities, admin credentials are sensitive secrets whose careless handling could expose full control over Node-RED flows and runtime settings.

Static analysis

No suspicious patterns detected.