T03 · Remote Payload Retrieval and Execution
- Location
references/installation-errors.md:32- Finding
Remote Installation Scripts Are Executed Directly Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a legitimate OpenClaw troubleshooting helper, but it includes under-scoped setup, credential, network-facing, package-install, and privilege-changing guidance that users should review carefully before installing.
Install only if you are comfortable reviewing and manually controlling setup and repair actions. Avoid running the remote curl-to-shell commands, do not make the Docker socket world-writable, change the generated gateway bind address/token before use, and store provider API keys with restrictive permissions or a secret manager.
references/installation-errors.md:32Remote Installation Scripts Are Executed Directly Without Integrity Verification
scripts/lib/setup_helpers.py:28Setup Wizard Stores Provider API Keys in Plaintext and Generates a Weak Network Gateway Token
references/sandbox-errors.md:38Troubleshooting Guidance Grants Root-Equivalent Access Through the Docker Socket
references/channel-errors.md:310Third-Party Executable Archive Is Installed Without Signature or Checksum Verification
SKILL.md:16Unpinned Dependencies and Automatic Global Package Installation Create Supply-Chain Risk
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
An interactive setup workflow that may install pnpm/OpenClaw, collect API keys, and generate or back up configuration files presents significant security and privacy risk if framed merely as diagnostics. The setup context makes this more dangerous because it invites users to disclose secrets and authorize modifications during first-run onboarding, when scrutiny is often lowest.
A self-updater in a skill is inherently high risk because it can modify local code, reference data, or execution behavior after initial review. In this context, the skill already combines diagnostics, setup, and recommendations, so self-modification further erodes reviewability and can expand capabilities over time without equivalent scrutiny.
python3 {baseDir}/scripts/enhanced-doctor.py --json
### Self-Updater
Keep references and caches current.
```bash
# Check what's outdated
The explicit '--update' action indicates the skill can change local state rather than only inspect it. Self-modifying or self-refreshing behavior is dangerous because it can introduce new code/data, invalidate previous review assumptions, and potentially consume untrusted remote content.
Keep references and caches current.
# Check what's outdated
python3 {baseDir}/scripts/self-updater.py --check
# Update everything
python3 {baseDir}/scripts/self-updater.py --update
Repeated self-update capability, including targeted updates, confirms the skill supports mutation of its own local assets or caches. Even if limited to data, self-modification can still alter recommendations, diagnostics, or future command behavior in ways not visible at review time.
python3 {baseDir}/scripts/self-updater.py --check
# Update everything
python3 {baseDir}/scripts/self-updater.py --update
# Update only skill cache
python3 {baseDir}/scripts/self-updater.py --update --skills-only
A skills-only update may be narrower than full self-update, but it still modifies local trusted state and may influence future recommendations or actions. In a recommendation and maintenance tool, changing cached skill data can affect what users are encouraged to install or run.
python3 {baseDir}/scripts/self-updater.py --update
python3 {baseDir}/scripts/self-updater.py --update --skills-only
### Setup Wizard
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
"title": "Context Window Exceeded",
"description": "Request exceeds model's context window limit",
"causes": ["Too many tokens in prompt", "Large conversation history", "Big file attachment", "Context accumulation"],
"fix_steps": ["Reduce prompt length", "Clear conversation history", "Use model with larger context window", "Implement context pruning"],
"fix_recipe_id": "fix-config-validate",
"related_codes": ["PAYLOAD_TOO_LARGE"],
"doc_url": "https://docs.openclaw.ai/models/context-limits"
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Gateway rejects AI provider requests
**Common Causes:**
- Missing API key in .env file
- Incorrect API key value
- API key not activated with provider
- Typo in environment variable name