ReefWatch

PassAudited by ClawScan on Feb 23, 2026.

Overview

ReefWatch's code, runtime instructions, and requested environment access are internally consistent with its stated purpose as a local host-based intrusion detection daemon, though it requires elevated file/log/network access and will install third‑party Python packages when enabled.

This skill appears to do what it claims: a local host-based intrusion detection daemon that alerts OpenClaw via a webhook. Before installing or enabling it, consider the following: - Review setup_rules.py and the rules download sources: rule updates are fetched from the network and will pull third-party YARA/Sigma rule repositories (expected, but verify the URLs and trust the sources). - The instructions install Python packages via pip from the skill's requirements.txt. Pip installs can run code/build native extensions (e.g., yara-python). Prefer installing in a virtualenv, container, or test machine first rather than globally. - The daemon reads system logs, enumerates processes, inspects network connections, and can hash files (including critical system files). These operations may require root/privileged access to be fully effective and will access sensitive data (e.g., auth logs, /etc). Only run if you accept that level of access. - By default the AlertManager refuses external webhooks unless webhook.allow_external is explicitly enabled; if you do enable external alerting, ensure the webhook URL is trustworthy and HTTPS is used. The skill stores logs/history under ~/.openclaw and writes a pid file to /tmp when started. - If you plan to run continuously, inspect the provided systemd/launchd service files before enabling them, and run the code in a controlled environment first (or audit the rule sets and config) to confirm it behaves as expected. Overall: coherent with its purpose (benign), but treat it like any privileged monitoring agent — review network rule downloads, run in an isolated environment to validate, and avoid installing globally without inspection.