ClawHub
Back to skill

Security audit

Pilot Swarm Task Farm Setup

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent setup guide for a five-node compute swarm, with expected but important operational risks around peer trust and Slack notifications.

Install only on hosts you control, verify each peer before running handshake commands, restrict port 1002 to trusted networks, and review the installed pilot-slack-bridge settings before sending alerts to Slack.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The README explicitly says the monitor reports to Slack but provides no warning about what data may be sent, how sensitive task metadata could leak, or how to constrain outbound reporting. In a distributed task farm, telemetry can include task names, filenames, queue state, and operational details that may expose sensitive business or workload information if forwarded to third-party services.

Missing User Warnings

High
Confidence
97% confidence
Finding
The documentation states that when both sides handshake, trust is auto-approved, but it does not warn users that this bypasses any meaningful human verification of peer identity. In a self-organizing swarm where nodes automatically join and exchange tasks/results, an attacker who can spoof naming, intercept setup, or trick an operator into handshaking the wrong host could gain trusted access to distribute malicious tasks, exfiltrate results, or poison monitoring data.

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The skill defines ongoing worker health telemetry to a monitor and includes a Slack alerting bridge, but does not disclose what operational data may leave the local swarm or be forwarded to third-party services. In a distributed compute setup, metrics, hostnames, task status, and failure details can reveal workload patterns and infrastructure metadata, making the omission a real privacy and data-governance risk.

Static analysis

No suspicious patterns detected.