T03 · Remote Payload Retrieval and Execution
- Location
README.md:44- Finding
Mutable Remote Installer Is Piped Directly into Bash
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
FounderClaw is a disclosed multi-agent/browser automation system, but its installer and local browser-control service expose enough high-impact authority that users should review it carefully before installing.
Install only if you are comfortable with a broad local agent system that modifies OpenClaw configuration, runs a browser daemon, and can use authenticated browser sessions. Prefer cloning and reviewing a pinned commit instead of using curl | bash, avoid importing cookies on shared or untrusted machines, and do not leave the browser daemon running while handling sensitive web accounts.
README.md:44Mutable Remote Installer Is Piped Directly into Bash
browse/src/server.ts:827Unauthenticated Health Endpoint Discloses the Browser-Control Bearer Token
browse/src/cookie-picker-routes.ts:83Cookie Discovery and Import Operations Are Exposed Without Authentication
browse/src/server.ts:848Browser References and Activity Are Exposed Through Unauthenticated Wildcard-CORS Endpoints
install.sh:59Installer Automatically Resolves Unpinned Third-Party Dependency Ranges
The architecture explicitly supports importing and decrypting browser cookies via macOS Keychain, then loading them into an automated browser context. Even with user approval and in-memory handling, this materially expands access to authenticated web sessions; compromise of the local daemon, token, or agent workflow could enable session hijacking or unauthorized actions using imported cookies.
Cookies are the most sensitive data founderclaw handles. The design:
1. **Keychain access requires user approval.** First cookie import per browser triggers a macOS Keychain dialog. The user must click "Allow" or "Always Allow." founderclaw never silently accesses credentials.
2. **Decryption happens in-process.** Cookie values are decrypted in memory (PBKDF2 + AES-128-CBC), loaded into the Playwright context, and never written to disk in plaintext. The cookie picker UI never displays cookie values — only domain names and counts.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
### Shell injection prevention
The browser registry (Comet, Chrome, Arc, Brave, Edge) is hardcoded. Database paths are constructed from known constants, never from user input. Keychain access uses `Bun.spawn()` with explicit argument arrays, not shell string interpolation.
## The ref system
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example and add your API key
cp .env.example .env
# Edit .env → set ANTHROPIC_API_KEY=sk-ant-...
# 2. Install deps (if you haven't already)
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example and add your API key
cp .env.example .env
# Edit .env → set ANTHROPIC_API_KEY=sk-ant-...
# 2. Install deps (if you haven't already)
bun install
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example and add your API key
cp .env.example .env
# Edit .env → set ANTHROPIC_API_KEY=sk-ant-...
# 2. Install deps (if you haven't already)
bun install
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example and add your API key
cp .env.example .env
# Edit .env → set ANTHROPIC_API_KEY=sk-ant-...
# 2. Install deps (if you haven't already)
bun install
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example and add your API key
cp .env.example .env
# Edit .env → set ANTHROPIC_API_KEY=sk-ant-...
# 2. Install deps (if you haven't already)
bun install
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example and add your API key
cp .env.example .env
# Edit .env → set ANTHROPIC_API_KEY=sk-ant-...
# 2. Install deps (if you haven't already)
bun install
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# 1. Copy .env.example and add your API key
cp .env.example .env
# Edit .env → set ANTHROPIC_API_KEY=sk-ant-...
# 2. Install deps (if you haven't already)
bun install
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).
Remove the project-local symlink. Claude Code falls back to founderclaw/:
rm .claude/skills/founderclaw
The per-skill symlinks (qa, ship, etc.) still point to founderclaw/..., so they'll
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.
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.
Piping downloaded content directly into bash compounds risk by immediately chaining network retrieval to code execution with no review boundary. In the context of this skill, the installer is expected to create files, modify OpenClaw configuration, add agents, and restart the gateway, so misuse or compromise could rapidly alter the local agent environment.
curl -fsSL https://raw.githubusercontent.com/ashish797/FounderClaw/main/install.sh | bash
Then say "install founderclaw" in chat to complete the multi-agent config.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.
An uninstaller that deletes repository files, removes symlinks, and edits OpenClaw configuration is a destructive capability that should be clearly separated from ordinary skill behavior. If triggered unexpectedly or without confirmation, it can remove local assets and corrupt user configuration.