Leak Check

PassAudited by ClawScan on May 1, 2026.

Overview

This appears to be a local leak-checking tool, but it intentionally reads sensitive OpenClaw session logs and a credential-fragment config file.

This skill looks coherent for its purpose. Before installing or running it, understand that it scans your local OpenClaw session history and uses a config file containing credential-identifying fragments. Store only partial fragments, keep the config private, and be careful with the optional command that deletes session log files.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Running the skill lets it inspect local OpenClaw session logs for configured credential fragments and output a report of matching sessions, providers, and models.

Why it was flagged

The script reads persistent OpenClaw session history and a credential-pattern config file. This is aligned with the stated leak-checking purpose, but those files can contain sensitive user context and credential-identifying data.

Skill content
const DEFAULT_SESSION_PATH = path.join(os.homedir(), '.openclaw', 'agents', 'main', 'sessions'); ... const OPENCLAW_CREDENTIALS_CONFIG = path.join(os.homedir(), '.openclaw', 'credentials', CONFIG_FILENAME);
Recommendation

Use only partial credential fragments, keep the config file private, and avoid sharing the output if session IDs, provider names, or credential labels are sensitive.

What this means

If the wrong session file is deleted, the user could lose local OpenClaw session history.

Why it was flagged

The documentation includes a user-directed file deletion command for clearing config echoes. It is scoped to a specific session log and not shown as automatic behavior, but it can delete local history if used incorrectly.

Skill content
To clear them, delete the session file from `~/.openclaw/agents/main/sessions/`: `rm ~/.openclaw/agents/main/sessions/<session-uuid>.jsonl`
Recommendation

Only run the deletion command after verifying the exact session UUID, and consider backing up the file instead of deleting it.