Security audit

Vvvv Custom Nodes

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly vvvv custom-node documentation, but one ready-to-copy example starts a WebSocket server by default without security scoping or access-control guidance.

Review before installing or using this skill for code generation. Most guidance is normal vvvv node-development material, but do not copy the WebSocket server example verbatim: default it off, bind to localhost unless remote access is intentional, add authentication and authorization, validate origins and messages, and document firewall/TLS requirements for any non-local use.

A.I.G

Vulnerability Patterns

Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally

Findings (1)

T09 · Insecure Skill Coding Practices

Warning

Location: examples.md:158
Finding: Default-Enabled WebSocket Server Lacks Explicit Access Controls
Content: View full analysis
/// Hosts a WebSocket server for external color grading UI. /// public void Update( out string status, out string lastError, int port = 9999, bool enabled = true) { lastError = null; if (port != _lastPort || enabled != _lastEnabled) { _server?.Stop(); _server = null; if (enabled) { try { _server = new WebSocketServer(port); _server.Start(); } catch (Exception ex) { lastError = ex.Message; } } _lastPort = port; _lastEnabled = enabled; } status = _server?.IsRunning == true ? $"Running on :{port}" : "Stopped"; } public void Dispose() { _server?.Stop(); _server = null; } } ``` ### Technical Analysis The example recommends a WebSocket service that is enabled by default and constructed using only a port number. It does not explicitly restrict the listening address to the loopback interface or demonstrate authentication, authorization, origin validation, transport encryption, message validation, connection limits, or rate limiting. The actual interface exposure depends on the unspecified `WebSocketServer` implementation and its default binding behavior. If it binds to all netwo ...[truncated 1796 chars]
Remediation: View remediation

SkillSpector

Vulnerability Patterns

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

Findings (2)

Description-Behavior Mismatch

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The manifest describes a skill focused on authoring node classes, pin configuration, change detection, stateless operation nodes, and service consumption via NodeContext. This example adds a WebSocket server that listens on a port and serves an external UI, which is a materially broader runtime/network capability than the stated code-pattern guidance.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: The Markdown provides a ready-to-copy WebSocket server example that listens on a configurable port without any warning about network exposure, authentication, interface binding, or deployment risk. In the context of a coding-assistance skill, users may reproduce this pattern verbatim and unintentionally expose a local or remote service, increasing the risk of unauthorized access or misuse.
Content: No source excerpt is available for this finding.