Back to skill

Security audit

openclaw-claude-dispatcher

Security checks for vulnerabilities and agentic risk

Overview

This skill dispatches coding work to a background Claude process with broad permissions and hard-coded external notifications, so it needs careful review before installation.

Install only if you control and trust the referenced dispatcher and notification hook, recognize the hard-coded Feishu/WeCom destinations, and are comfortable with background coding tasks. Prefer an approval-requiring permission mode, explicitly confirm the project directory and notification recipient for each run, and review task outputs or diffs before relying on the result.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Tool Hijacking and SpoofingModifies or replaces tools so legitimate-looking calls execute attacker logic
  • 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
Findings (4)

T01 · Skill Instruction Hijacking

Error
Location
SKILL.md:3
Finding

Broad Trigger Rules Hijack Coding Workflows and Suppress Result Review

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Error
Location
SKILL.md:83
Finding

Delegated Coding Tasks Default to Unrestricted Permission Bypass

Content
View full analysis
Remediation
View remediation

other

Error
Location
SKILL.md:47
Finding

Task Completion Data Is Sent to Hard-Coded External Recipients

Content
View full analysis
Remediation
View remediation

T07 · Tool Hijacking and Spoofing

Error
Location
SKILL.md:64
Finding

Mandatory Invocation of an Unbundled and Unverified Local Dispatcher

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Rogue AgentSelf-Modification, Session Persistence
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (7)

Vague Triggers

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The trigger criteria are extremely broad and overlap with routine coding requests, causing this skill to auto-activate for a wide range of normal development tasks. In context, that is dangerous because activation leads users toward dispatching unattended external code-execution workflows rather than keeping work in the current controlled session.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill instructs use of unattended code modification with --permission-mode bypassPermissions as the default, but does not require a prominent warning or explicit informed consent from the user before launching autonomous changes. This is dangerous because users may unknowingly authorize broad file modifications and command execution in their project without understanding the trust and change-control implications.

Content

No source excerpt is available for this finding.

Session Persistence

Medium
Category
Rogue Agent
Confidence
77% confidence
Finding

The skill is designed to launch long-running background tasks with completion callbacks, which creates persistence beyond the immediate session. While persistence is part of the intended functionality, it becomes security-relevant because it enables deferred autonomous code generation/modification and off-session notifications that may continue after the user's active oversight ends.

Content

Scanner excerpt · SKILL.md (reported line 7)May include surrounding context.

md
Dispatch long-running coding tasks to Claude Code CLI with automatic callback notifications to Feishu/WeCom when complete.

  Use this skill whenever the user wants to:
  - Create a new project or application from scratch
  - Modify/upgrade an existing project with new features
  - Refactor or improve existing code
  - Run any coding task that might take a long time

File System Enumeration

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.

Content

Scanner excerpt · SKILL.md (reported line 236)May include surrounding context.

md
Common issues:
1. **Working directory doesn't exist** - Create it first with `mkdir -p`
2. **Nested Claude Code session** - Can't run Claude Code inside Claude Code. User should run from a regular terminal.
3. **Permission denied** - Check if dispatch script is executable: `ls -l ~/openclaw/scripts/dispatch-claude-code.sh`

### Checking system status

File System Enumeration

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.

Content

Scanner excerpt · SKILL.md (reported line 244)May include surrounding context.

bash
# Check if hook is installed
ls -la ~/.claude/hooks/notify-agi.sh

# Check if dispatch script exists
ls -la ~/openclaw/scripts/dispatch-claude-code.sh

File System Enumeration

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.

Content

Scanner excerpt · SKILL.md (reported line 247)May include surrounding context.

bash
# Check if hook is installed
ls -la ~/.claude/hooks/notify-agi.sh

# Check if dispatch script exists
ls -la ~/openclaw/scripts/dispatch-claude-code.sh

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
95% confidence
Finding

The skill explicitly recommends autonomous operation modes such as dontAsk and defaults to bypassPermissions, normalizing execution and editing behavior without interactive approval. In a coding-dispatch skill that can modify arbitrary project files, this increases the chance of unintended destructive changes, unsafe commands, or execution beyond what the user expected.

Content

Scanner excerpt · SKILL.md (reported line 270)May include surrounding context.

md
Choose based on the task:

- `bypassPermissions` - No prompts, fully automated (recommended default)
- `dontAsk` - Run without asking, but still show what's happening
- `acceptEdits` - Safer for critical codebases, but requires some interaction

Default to `bypassPermissions` unless the user expresses concern about automated changes.