Caveat verdict
openclaw-sync-bridge
The install step uses curl piped to bash from an external host, and the skill syncs SOUL.md, AGENTS.md, IDENTITY.md, and all skills to a GitHub Gist, which represents a broad upload of agent identity and configuration data to a third-party service.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
Permission integrity
network_out
Findings (5)
Pipe-to-shell pattern (curl | sh) — supply chain attack vector
SKILL.md · code · curl -fsSL https://clawhub.ai/JayShna/openclaw-sync-bridge/install.sh | bash
Pipe to bash — executes piped content as shell commands
SKILL.md · code · | bash
Possible hardcoded credential
sync_bridge.py · prose · downgraded · Token: ").strip()
else:
token = cfg[
Python urllib.request — network access
sync_bridge.py · prose · downgraded · urllib.request
Python shutil file operation — copies/moves/deletes files
sync_bridge.py · prose · downgraded · shutil.copytree(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class A/B/E). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
No declared permissions — minimal attack surface.
network_out Is this flag fair?
Thanks — recorded.