Caveat verdict
openclaw-watchdog
Self-healing gateway monitor that sends alerts via the user own Telegram bot using credentials the user explicitly provides; diagnostics run locally.
⚠ 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.
Findings (7)
Recursive delete from root or home — destructive command
SKILL.md · code · rm -rf ~
HTTP request to bare IP address — common in malicious payloads
openclaw-watchdog/scripts/watchdog.py · prose · downgraded · http://127.0.0.1
subprocess execution — runs system commands from Python
openclaw-watchdog/scripts/watchdog.py · prose · downgraded · subprocess.check_output(
Python urllib.request — network access
openclaw-watchdog/scripts/test-message.py · prose · downgraded · urllib.request
Python os.getenv — reads environment variable
openclaw-watchdog/scripts/watchdog.py · prose · downgraded · os.getenv(
Python aiohttp session — async network access
openclaw-watchdog/scripts/watchdog.py · prose · downgraded · aiohttp.ClientSession
Python os.environ.get — reads environment variable
scripts/watchdog.py · prose · downgraded · os.environ.get(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
Requires 2 environment variables. (1 sensitive: TELEGRAM_TOKEN). Requires 2 system binaries.
credential_access Is this flag fair?
Thanks — recorded.