Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

OpenClaw Sync Bridge

v2.0.0

Automatically sync local and cloud OpenClaw configurations via private GitHub Gist with token-based setup and full overwrite synchronization.

0· 96·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description (sync OpenClaw workspace via GitHub Gist) align with included code and docs: the Python code implements push/pull/diff/status/backup against GitHub Gist and SKILL.md documents these operations.
Instruction Scope
Runtime instructions (setup/push/pull/diff/status/backup) stay within the described sync scope. The skill asks for a GitHub token and workspace path which is expected. It claims not to upload sensitive files and the code contains ignore rules for such files, though there are minor implementation quirks (see environment_proportionality / implementation notes).
!
Install Mechanism
SKILL.md/README instructs users to curl and pipe a script from https://clawhub.ai/JayShna/openclaw-sync-bridge/install.sh | bash (and a PowerShell equivalent). That is a higher-risk delivery channel because the domain is not a standard release host (GitHub releases) and piping remote scripts to shell executes remote code before you inspect it. The package does include install.sh and sync_bridge.py locally, so manual/local install is possible and safer.
Credentials
The skill only needs a GitHub token with gist permission to operate; that is proportional to its purpose. The docs and code reference optional environment variables (OPENCLAW_WORKSPACE, OPENCLAW_STATE_DIR) for convenience; registry metadata listed no required env vars which is acceptable. The token is stored in a local sync_config.json and IGNORE_PATTERNS include sync_config.json so the token should not be uploaded — this is consistent with the stated design.
Persistence & Privilege
The installer modifies user shell rc files (~/.bashrc, ~/.zshrc) to add an alias and may create $HOME/.local/bin/sync-bridge; these are user-level changes (not system-wide). always:false and normal autonomous invocation settings are used. This is expected for a convenience installer but users should be aware it edits dotfiles.
What to consider before installing
What to consider before installing: - Don't pipe remote scripts to your shell without review. The README/ SKILL.md recommend curl | bash from clawhub.ai — prefer to inspect the script first or use the included local files (install.sh, sync_bridge.py) bundled in the skill. - The skill needs a GitHub token with gist permission. Limit the token scope to only 'gist' and consider using a token dedicated to syncing (not your primary account token). - The code appears to only communicate with api.github.com for Gist operations; sync_config.json (which stores the token) is listed in the ignore rules and should not be uploaded. Still, inspect the code (sync_bridge.py) yourself before trusting it — some parts of the file were truncated in the review and a full read mitigates risk. - The installer will add an alias to your shell rc files and may create $HOME/.local/bin; expect these user-level modifications and back up your dotfiles first. - If you want to be cautious: install locally by copying the included files to a folder, run the local install.sh after reading it, or run python3 sync_bridge.py directly from the package directory. Consider testing in an isolated or disposable environment first. - If you plan to sync across devices, verify the IGNORE_PATTERNS actually cover all sensitive files you don't want uploaded. There is a small implementation nuance where file ignore logic uses substring checks which could have unintended effects — review the code and confirm sensitive files are never sent. If you want, I can: (a) point out the exact lines in sync_bridge.py that implement ignores, create/update Gists, and read/write the token, or (b) produce a safe, minimal checklist and commands to install without contacting clawhub.ai.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bm60dh1bd8ec7tp390c4jc583fkn9

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments