T08 · Insecure Dependencies
- Location
README.md:203- Finding
Unverified Archives Downloaded from Inconsistent Repository Identities
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
Context Bridge is not malicious, but it persistently collects and auto-loads broad OpenClaw metadata in ways users should review before installing.
Install only if you want OpenClaw to maintain cross-session memory and registries. Before running setup, review what it will copy into ~/.openclaw, especially cron payloads, agent workspace paths, and model handoff notes; remove sensitive entries, restrict file permissions, and avoid the direct archive commands unless you can verify the source and checksum.
README.md:203Unverified Archives Downloaded from Inconsistent Repository Identities
scripts/setup.sh:24Setup Collects and Duplicates Excessive OpenClaw Operational Metadata
scripts/setup.sh:323Persistent Session Loading Trusts Mutable and Partially Untrusted Content
The handoff memory feature is explicitly designed to persist session-to-session context, recent actions, and active projects, but the documentation omits any warning about retention, visibility across sessions/models, or the sensitivity of stored activity logs. That omission can cause users to unknowingly retain and disclose private operational history beyond the original session.
The README instructs automatic reading of multiple persistent context files, including user and memory data, at every session start without any privacy warning, consent step, or scope limitation. This creates a real risk of unnecessary exposure of sensitive historical data to whichever model/session is active, especially in cross-model or shared-environment use.
The skill establishes persistent directories and a session-start mechanism intended to reload context automatically, enabling durable state across sessions and models. In this skill's context, persistence is the core feature, which makes the risk more significant because it increases the likelihood that stale, sensitive, or over-broad context is silently reused in later interactions.
3. Create initial registries:
```bash
mkdir -p ~/.openclaw/model-agnostic-memory
mkdir -p ~/.openclaw/agents/defaults
The release notes directly instruct users to execute ./setup.sh without explaining what the script does, what privileges it may require, or warning that it will run arbitrary code on the user's machine. In a skill-installation context, this increases social-engineering risk because users may treat release notes as trusted operational guidance and execute the script without review.
This skill is designed to persist and rehydrate context across sessions by creating registries and a model-handoff memory file, which is a form of session persistence. In this context, persistence is the core feature, but it still creates security risk because sensitive actions, projects, and environment metadata can survive session boundaries and be exposed to future agents or models without strong access controls or minimization.
# 1. Install the skill
openclaw skills install https://github.com/loudmouthedmedia/context-bridge
# 2. Run setup to create registry files
cd ~/.openclaw/workspace/skills/context-bridge/scripts
./setup.sh
The skill explicitly auto-discovers local skills, crons, agents, and model handoff data, but it does not warn users that this aggregates potentially sensitive local metadata into model-readable context. This omission increases the risk of unintended disclosure of filesystem structure, agent definitions, scheduled jobs, and historical session information to the assistant or downstream systems.
The manual trigger phrase load context is broad and underspecified, which can cause the agent to read and aggregate multiple local context files without clear user confirmation, scope limits, or file boundaries. In this skill, that behavior is more dangerous because the referenced files include registries, agent configs, and handoff memory that may contain sensitive local operational data across sessions.
The script header claims it only creates and populates registry files, but it also writes persistent behavioral artifacts such as a session-start hook and a helper script under ~/.openclaw. This mismatch is security-relevant because it can mislead reviewers and users about the script’s true persistence and influence over future sessions, reducing informed consent and making hidden behavior easier to smuggle in.
The script establishes persistent state under ~/.openclaw, including directories intended to hold model memory, agent defaults, scripts, and skills. In this skill context, persistence is more dangerous because later parts of the script populate these locations with files that shape future agent behavior, creating durable influence beyond a one-time setup run.
echo "=== Context Bridge Setup ==="
echo ""
# Create directories
echo "Creating directories..."
mkdir -p ~/.openclaw/model-agnostic-memory
mkdir -p ~/.openclaw/agents/defaults
This section writes persistent registry files into ~/.openclaw that are later intended to be read automatically by models and tooling. Although registry creation can be legitimate, in this context the files become part of a durable control plane for future sessions, so silent creation or overwriting can alter agent behavior, available-skill discovery, and contextual loading without clear user review.
# CREATE/UPDATE REGISTRY FILES
# ============================================================================
# Create skills-registry.json
echo ""
echo "Creating skills-registry.json..."
cat > ~/.openclaw/skills-registry.json << EOF