Skill flagged — suspicious patterns detected

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

Multi-Device Sync via GitHub

v1.0.2

Multi-device OpenClaw data synchronization using GitHub. Manages workspace data sync across multiple machines (Ubuntu, Mac, etc.) with automatic push on file...

1· 317·0 current·0 all-time
byLeon@regulusz
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the implementation: scripts perform git clone/push/pull, create symlinks from ~/.openclaw/workspace into ~/openclaw-sync, run a push watcher and periodic pull daemon. Requested permissions/variables are minimal and consistent (no unexpected cloud credentials or unrelated services).
Instruction Scope
Runtime instructions and installer perform high-impact local operations appropriate for a sync tool: creating/removing files and directories, creating symlinks, copying workspace data into the sync repo, starting background daemons, and running git operations (commit/push/pull/rebase). These operations are in-scope for a synchronization tool but are destructive if misconfigured (rm -rf, replacing workspace files after backup). The SKILL.md / installer suggests syncing 'skills/' and memory files — this can cause private data or other skill files to be placed under git version control; user should carefully choose which paths to sync. Also note some installer calls have a likely typo (calls like sync-init.sh.sh), which is a bug but not evidence of malice.
Install Mechanism
No formal install spec in registry; SKILL.md offers a convenience one-liner that pipes raw.githubusercontent.com content into bash (curl | bash). raw.githubusercontent.com is a common host for installers, but piping remote scripts to shell is intrinsically risky—recommended to git clone and inspect the repository before running. The shipped bundle already includes the installer and scripts so a local install (clone + review + run) is safer.
Credentials
The skill declares no required environment variables or credentials, which matches the code: it uses local git/SSH configuration for authentication (the user’s existing SSH keys or credential helpers). There are no hidden external endpoints; sync-notify.sh mentions Feishu but falls back to writing local notification files and printing. No disproportionate credential requests were found.
Persistence & Privilege
The scripts create persistent artifacts in the user home (~/.config/openclaw, ~/.openclaw, ~/openclaw-sync), start background processes (daemon + push watcher) and write log/PID files. This is expected for a long-running sync service, but it does give the skill ongoing presence on the machine and will run periodically until stopped—review/stop the daemon if you uninstall. always:false and no elevated persistent privileges were requested.
Assessment
What to consider before installing: - Review code locally instead of running the curl | bash one-liner. Clone the repo (git clone https://github.com/RegulusZ/multi-device-sync-github.git) and inspect install.sh and the scripts before executing. - Back up your workspace first. The installer will create symlinks and may remove original files (it does back them up by default in many cases, but verify backups exist before proceeding). - Be deliberate about which paths you sync. Avoid syncing 'skills/' or other directories that may contain secrets, credentials, nested .git folders, or private configuration unless you understand the consequences. - Use a private GitHub repository as recommended. If you accidentally push sensitive data, Git history can retain it—plan for .gitignore and history cleaning if needed. - Verify authentication: the scripts rely on your existing git/SSH configuration; you will need working SSH keys or credential helpers for push/pull. - Note the installer has small bugs (calls like sync-init.sh.sh). If you see execution errors, run the scripts manually from the cloned repo and fix the call names before running automated steps. - If you want lower-risk testing, run the installer in a throwaway VM/container or test user account first to confirm behavior. If you can share the exact repo URL or want, I can point out the exact lines that (1) delete files, (2) start daemons, and (3) would commit which paths so you can audit them quickly.

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

latestvk975rnaansnwfw5fvm0cnqnfrd823jkq

License

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

Comments