T01 · Skill Instruction Hijacking
- Location
CLAUDE.md:5- Finding
Auto-Injected Instructions Attempt to Override Session-Wide Agent Authorization Policy
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is disclosed and not visibly malicious, but it broadly tells the agent to read files, search, and browse directories without approval across sessions, which needs review before use.
Install only if you want a persistent CRUD approval workflow that lets the agent perform read operations without a second confirmation. Review or modify it first if your environment contains secrets, private repositories, logs, credentials, or other sensitive files that should require explicit approval before being read or searched.
CLAUDE.md:5Auto-Injected Instructions Attempt to Override Session-Wide Agent Authorization Policy
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).
rmdir /S /Q %USERPROFILE%.openclaw\skills\crud
rm -rf ~/.openclaw/skills/crud
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).
rmdir /S /Q %USERPROFILE%.openclaw\skills\crud
rm -rf ~/.openclaw/skills/crud
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
You are now using CRUD Approval Mode. Please strictly follow these principles:
1. **Read** - Fully unrestricted, no approval needed, execute directly
2. **Create, Update/Edit, and Delete** - Must first return an action list and wait for user's secondary confirmation before executing
---
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## 📌 Memory Tips
1. **Read = Fast** - No approval needed, prioritize efficiency
2. **Create/Update/Delete = Safe** - Must confirm, prevent accidental operations
3. **No Exceptions** - All write operations require confirmation
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
# CRUD Skill Usage Examples
## Scenario 1: Read File (No Approval Needed)
**User:** Help me see the content of main.py
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
# CRUD Skill Usage Examples
## Scenario 1: Read File (No Approval Needed)
**User:** Help me see the content of main.py
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
**User:** Help me see the content of main.py
**Your Response:**
Directly call Read tool to read file, no confirmation needed
---
This markdown file provides uninstall commands that recursively and forcefully delete the skill directory using rmdir /S /Q and rm -rf, but it does not warn users that these commands are destructive and irreversible. Under the markdown-specific missing-warning rule, documentation should disclose behaviors that could affect user data or system integrity.
The README explicitly defines a policy where read operations are executed without user approval. In an agent skill, unrestricted reads can expose sensitive local files, credentials, tokens, configuration, or proprietary code if the agent misclassifies a request as 'read' or if a prompt induces broad data access. The surrounding context makes this more dangerous because it is presented as an automatic security control, which may encourage operators to trust a policy that still permits data exfiltration paths.
| Operation Type | Approval Required | Description |
|---------------|-------------------|-------------|
| **Read** | ❌ No Approval | File reading, search queries, etc. |
| **Create** | ✅ Requires Confirmation | File creation, new skill creation, etc. |
| **Update/Edit** | ✅ Requires Confirmation | File modification, code editing, etc. |
| **Delete** | ✅ Requires Confirmation | File deletion, directory removal, etc. |
The workflow states that read requests are executed directly with no approval step. This creates an autonomous decision path for data-access operations, allowing the agent to retrieve and return sensitive information without a user checkpoint, especially in cases of ambiguous intent, overbroad search, or prompt-injection-driven file discovery. Because this is described as an operational workflow, it is more than incidental wording and indicates intended behavior.
User Request → Execute Directly → Return Result
The skill explicitly authorizes unrestricted read operations, including file reading, search, and directory browsing, without any approval gate. In an agent context, reads can expose secrets, credentials, proprietary code, or sensitive filesystem metadata, so treating them as inherently safe is an unsafe autonomous decision policy.
| Operation Type | Approval Required | Description |
|---------------|------------------|-------------|
| **Read** | ❌ No approval | File reading, search queries, directory browsing, etc. |
| **Create** | ✅ Requires confirmation | File creation, new skill creation, directory creation, etc. |
| **Update/Edit** | ✅ Requires confirmation | File modification, code editing, config updates, etc. |
| **Delete** | ✅ Requires confirmation | File deletion, directory deletion, skill deletion, etc. |
The workflow instructs the agent to execute read requests directly with no approval step. This creates a clear path for autonomous data access and exfiltration because attackers can phrase malicious objectives as read-only operations while still obtaining sensitive information.
User Request → Execute Directly → Return Result
The stated use case promotes approval-free read operations as a productivity feature, reinforcing a policy that undervalues confidentiality risk. In practice, unrestricted reads can be chained with summarization or reporting to leak sensitive contents even when no write action occurs.
## Use Cases
- Daily development: Quick read operations without approval restrictions
- Critical operations: Confirmation mechanism before all write operations
- Skill development: New skill creation requires confirmation for safety
This markdown file includes the user example "Help me see the content of main.py," where the trigger phrase "Help me" is a common everyday expression rather than a narrowly scoped invocation. Without additional negative examples or explicit trigger constraints, this can suggest an activation pattern that is broader than intended.
No suspicious patterns detected.