T05 · Unauthorized Access and Privilege Escalation
- Location
references/multi-agent-recipes.md:290- Finding
Cross-Agent Session Transcript Access Weakens Agent Isolation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a mostly coherent OpenClaw administration guide, but it includes under-scoped guidance for sharing another agent's session transcripts and other high-impact admin patterns users should review carefully.
Install only from a source and revision you trust. Before using recipes that enable cross-agent memory search, agent-to-agent access, daemon/service install, cron, plugins, skills, or provider changes, review the exact config change and keep it narrowly scoped. Prefer HTTPS or encrypted tunnels for non-loopback model endpoints, store credentials in environment or secret references, and keep the skill's explicit confirmation and backup steps in place.
references/multi-agent-recipes.md:290Cross-Agent Session Transcript Access Weakens Agent Isolation
references/models-and-providers.md:404Bearer Credentials and Model Traffic Shown over Unencrypted LAN HTTP
README.md:45Installation Instructions Retrieve Mutable Unpinned External Content
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
Clone into your Codex skills directory:
mkdir -p ~/.codex/skills
git clone https://github.com/ramensushi2026/openclaw-cli-skill.git ~/.codex/skills/openclaw-cli
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Clone into your Codex skills directory:
mkdir -p ~/.codex/skills
git clone https://github.com/ramensushi2026/openclaw-cli-skill.git ~/.codex/skills/openclaw-cli
The description says to use this skill whenever the user asks how to run, configure, or troubleshoot any openclaw command or concept, followed by a very expansive list. This broad trigger lacks exclusion conditions or negative examples, so it may cause the skill to activate for almost any OpenClaw-related discussion, including cases where a narrower skill might be more appropriate.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
2. Run `openclaw doctor`.
3. If any errors, **ABORT** the bounce.
- **BACKUP INTEGRITY:** Maintain a rotating history of up to 3 validated backups (`openclaw.json.bak.1` to `.bak.3`). After a verified successful bounce, prune any backups older than 24 hours and maintain the most recent 3 verified snapshots.
- **SECRET HYGIENE:** Never write credential-like patterns (`PAT`, `TOKEN`, `KEY`) into any workspace file. Before removing any existing configuration that contains keys/credentials, ensure they are secured in the environment (`~/.openclaw/credentials/.env`) first.
- **EXPLICIT AUTHORIZATION:** I must never make changes to the `openclaw.json` or system configuration without *first* proposing the change, explaining the "Why," and obtaining explicit user permission.
- **EXTERNAL SKILL AUDIT:** Never install a skill from ClawHub or any external repository without *first* inspecting the source code. Look specifically for:
- Exfiltration of data/tokens to unknown URLs.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Examples:
# Non-streaming
curl -sS http://127.0.0.1:18789/v1/chat/completions \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"model":"openclaw/default","messages":[{"role":"user","content":"hi"}]}'
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
openclaw gateway start # start as background service
openclaw gateway stop
openclaw gateway restart
openclaw gateway install # register launchd/systemd
openclaw gateway uninstall
openclaw gateway health # fetch health via RPC
openclaw gateway status # show service state
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
openclaw sandbox list
openclaw sandbox list --browser
openclaw sandbox recreate --all
openclaw sandbox recreate --agent coding
openclaw sandbox explain --agent coding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"mode": "merge",
"providers": {
"<provider-id>": {
"baseUrl": "https://api.example.com/v1",
"apiKey": "${MY_API_KEY}",
"api": "openai-completions",
"models": [
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"mode": "merge",
"providers": {
"<provider-id>": {
"baseUrl": "https://api.example.com/v1",
"apiKey": "${MY_API_KEY}",
"api": "openai-completions",
"models": [
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"mode": "merge",
"providers": {
"<provider-id>": {
"baseUrl": "https://api.example.com/v1",
"apiKey": "${MY_API_KEY}",
"api": "openai-completions",
"models": [
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"mode": "merge",
"providers": {
"moonshot": {
"baseUrl": "https://api.moonshot.ai/v1",
"apiKey": "${MOONSHOT_API_KEY}",
"api": "openai-completions",
"models": [
The document explicitly shows how one agent can search another agent's session transcripts by adding that agent's sessions directory as an extra collection, but it provides no warning that this bypasses normal isolation expectations and exposes prior conversation contents. In a multi-agent system where agents are described as isolated by workspace/auth/session boundaries, documenting cross-agent transcript access without privacy and consent guidance can lead to accidental overexposure of sensitive data.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -sS http://127.0.0.1:18789/v1/chat/completions \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{
The markdown documents openclaw models scan --set-default and --yes as convenience commands, but it does not warn that these options can automatically change the selected model/provider without an explicit user review step. Because switching models may send future prompts and related data to a different external provider, a brief disclosure would better inform users of the privacy and operational impact.
No suspicious patterns detected.