ReefWatch
v1.3.0Continuous local security monitoring daemon for Linux and macOS. Detects brute-force attacks, malware, privilege escalation, suspicious processes, file tampe...
⭐ 0· 496·0 current·0 all-time
byYassin Naeim@yasnaak
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (HIDS) match the actual code and runtime requirements: the package contains collectors for logs, files, processes, and network, detection engines (YARA, Sigma, custom rules), and an alert manager that posts to an OpenClaw webhook. Required binaries (python3, pip3) and the single env var (OPENCLAW_HOOKS_TOKEN for webhook auth) are proportionate to the described functionality.
Instruction Scope
SKILL.md instructions are narrowly scoped to installing Python deps, downloading rule sets (setup_rules.py), starting/stopping a local daemon, and invoking manual scans. These actions will read system logs, network state, process lists, and watched filesystem paths (including potentially sensitive paths such as /etc), which is expected for a HIDS but requires appropriate privileges and user awareness. The skill claims 'data stays local' but the webhook can be configured to send alerts externally if webhook.allow_external is set — by default the code refuses non-local webhooks unless explicitly allowed.
Install Mechanism
The skill is instruction-only (no platform install manifest) but ships full Python source and a requirements file and instructs to run pip3 install -r from the skill workspace. This is expected, but pip installing packages (yara-python, psutil, requests) may build native extensions and can run code at install time. setup_rules.py likely downloads rule sets from GitHub (expected for YARA/Sigma rules) — rule downloads are normal but represent external network activity that should be reviewed.
Credentials
Only OPENCLAW_HOOKS_TOKEN is declared and used to authenticate to the local OpenClaw webhook; this is appropriate. The skill does not request unrelated secrets or other environment credentials. Note: runtime behavior may require elevated OS permissions (reading system logs, network sockets, /etc/*) which are not declared as env vars but are inherent to HIDS operation.
Persistence & Privilege
The skill runs as a background daemon and provides instructions to launch as a user systemd/launchd service, which is appropriate for continuous monitoring. always:false (not force-included) and no modification of other skills observed. However, running the daemon (and enabling system service) grants continuous background access to system logs/files/network; review and run with least privilege and inspect service files before enabling system-wide.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
latestvk970mg2w34sratztkzdja2p9fd81p70q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
OSLinux · macOS
Binspython3, pip3
EnvOPENCLAW_HOOKS_TOKEN
