T03 · Remote Payload Retrieval and Execution
- Location
install.sh:6- Finding
Mutable Remote Installer Is Recommended for Direct Shell Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
Swarm is a coherent LLM parallel-processing skill, but its install path and unauthenticated local daemon create real risk around paid API use and cached responses.
Install only if you trust the publisher and can run it in a controlled local environment. Avoid curl-to-bash installation, inspect or pin the source first, keep provider-side spending limits enabled, do not expose port 9999 to other machines or browsers you do not trust, and avoid sending sensitive prompts unless caching is disabled or the cache directory is properly protected.
install.sh:6Mutable Remote Installer Is Recommended for Direct Shell Execution
lib/daemon.js:1347Unauthenticated LLM Daemon Is Exposed Beyond the Localhost Boundary
lib/daemon.js:1291Unbounded HTTP Request Body Enables Memory Exhaustion
config.js:89Advertised Daily Spending Limits Are Not Enforced
lib/cache.js:35Plaintext Prompt Cache Can Leak Responses and Return Cross-Input Results
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
view` — Dry-run to see pipeline plan without executing
- 7 task pattern detectors (comparative, research-deep, adversarial, filter-refine, multi-perspective, opportunity, summarize)
- 4 depth presets: quick (2 stages), standard (4), deep (5-6), exhaustive (8)
- Smart perspective selection based on task keywords
- **Capabilities discovery** — `GET /capabilities` endpoint for orchestrator LLMs
- Lists all execution modes, perspectives, transforms, and depth presets
- `swarm capabilities` CLI command
- **Benchmark** — Quality comparison tool (single vs parallel vs chain)
- `POST /benchmark` — Runs same task through all 3 modes
- LLM-as-judge scoring on 6 dimensions (accuracy, depth, completeness, coherence, actionability, nuance)
- Cost/quality ratio comparison table
- Based on G-Eval/FLASK evaluation methodology
- **Worker perspective override** — Chain stages inject custom system prompts per worker
### Changed
- Client library: added `chain()`, `chainSync()`
This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.
### Security
- Workers now refuse to output API keys, tokens, or credentials
- External content treated as DATA, not instructions
- Injection attempts like "ignore all previous instructions" are logged and ignored
- Credentials patterns (Google, OpenAI, Anthropic, GitHub, Slack) auto-redacted from output
## [0.2.0] - 2026-01-25
Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
### 1. Make your code changes
Edit files in `~/clawd/skills/node-scaling/`
### 2. Update SKILL.md
Update the root `SKILL.md` with any new features, endpoints, or config changes. This is what the agent reads.
### 3. Bump version
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# Clean slate
rm -rf /tmp/swarm-publish
mkdir -p /tmp/swarm-publish/references
# Copy docs only
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
# Clean slate
rm -rf /tmp/swarm-publish
mkdir -p /tmp/swarm-publish/references
# Copy docs only
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.
The skill documentation includes live web research and implies fetching/analyzing multiple URLs, but the top-level metadata does not clearly declare these outbound data access behaviors. This matters because users may provide confidential prompts or URLs assuming local orchestration, while the skill can transmit those inputs to network services and retrieve remote content.