Get the FREE Ultimate OpenClaw Setup Guide →
a

Openclaw Security Monitor

Verified

@adibirzu

npx machina-cli add skill @adibirzu/openclaw-security-monitor --openclaw
Files (1)
SKILL.md
7.7 KB
<!-- {"requires":{"bins":["bash","curl"]}} -->

Security Monitor

Real-time security monitoring with threat intelligence from ClawHavoc research, daily automated scans, web dashboard, and Telegram alerting for OpenClaw.

Commands

Note: Replace <skill-dir> with the actual folder name where this skill is installed (commonly openclaw-security-monitor or security-monitor).

/security-scan

Run a comprehensive 32-point security scan:

  1. Known C2 IPs (ClawHavoc: 91.92.242.x, 95.92.242.x, 54.91.154.110)
  2. AMOS stealer / AuthTool markers
  3. Reverse shells & backdoors (bash, python, perl, ruby, php, lua)
  4. Credential exfiltration endpoints (webhook.site, pipedream, ngrok, etc.)
  5. Crypto wallet targeting (seed phrases, private keys, exchange APIs)
  6. Curl-pipe / download attacks
  7. Sensitive file permission audit
  8. Skill integrity hash verification
  9. SKILL.md shell injection patterns (Prerequisites-based attacks)
  10. Memory poisoning detection (SOUL.md, MEMORY.md, IDENTITY.md)
  11. Base64 obfuscation detection (glot.io-style payloads)
  12. External binary downloads (.exe, .dmg, .pkg, password-protected ZIPs)
  13. Gateway security configuration audit
  14. WebSocket origin validation (CVE-2026-25253)
  15. Known malicious publisher detection (hightower6eu, etc.)
  16. Sensitive environment/credential file leakage
  17. DM policy audit (open/wildcard channel access)
  18. Tool policy / elevated tools audit
  19. Sandbox configuration check
  20. mDNS/Bonjour exposure detection
  21. Session & credential file permissions
  22. Persistence mechanism scan (LaunchAgents, crontabs, systemd)
  23. Plugin/extension security audit
  24. Log redaction settings audit
  25. Reverse proxy localhost trust bypass detection
  26. Exec-approvals configuration audit (CVE-2026-25253 exploit chain)
  27. Docker container security (root, socket mount, privileged mode)
  28. Node.js version / CVE-2026-21636 permission model bypass
  29. Plaintext credential detection in config files
  30. VS Code extension trojan detection (fake ClawdBot extensions)
  31. Internet exposure detection (non-loopback gateway binding)
  32. MCP server security audit (tool poisoning, prompt injection)
bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/scan.sh

Exit codes: 0=SECURE, 1=WARNINGS, 2=COMPROMISED

/security-dashboard

Display a security overview with process trees via witr.

bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/dashboard.sh

/security-network

Monitor network connections and check against IOC database.

bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/network-check.sh

/security-remediate

Scan-driven remediation: runs scan.sh, skips CLEAN checks, and executes per-check remediation scripts for each WARNING/CRITICAL finding. Includes 32 individual scripts covering file permissions, exfiltration domain blocking, tool deny lists, gateway hardening, sandbox configuration, credential auditing, and more.

# Full scan + remediate (interactive)
bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/remediate.sh

# Auto-approve all fixes
bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/remediate.sh --yes

# Dry run (preview)
bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/remediate.sh --dry-run

# Remediate a single check
bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/remediate.sh --check 7 --dry-run

# Run all 32 remediation scripts (skip scan)
bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/remediate.sh --all

Flags:

  • --yes / -y — Skip confirmation prompts (auto-approve all fixes)
  • --dry-run — Show what would be fixed without making changes
  • --check N — Run remediation for check N only (skip scan)
  • --all — Run all 32 remediation scripts without scanning first

Exit codes: 0=fixes applied, 1=some fixes failed, 2=nothing to fix

/security-setup-telegram

Register a Telegram chat for daily security alerts.

bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/telegram-setup.sh [chat_id]

Web Dashboard

URL: http://<vm-ip>:18800

Dark-themed browser dashboard with auto-refresh, on-demand scanning, donut charts, process tree visualization, network monitoring, and scan history timeline.

Service Management

launchctl list | grep security-dashboard
launchctl unload ~/Library/LaunchAgents/com.openclaw.security-dashboard.plist
launchctl load ~/Library/LaunchAgents/com.openclaw.security-dashboard.plist

IOC Database

Threat intelligence files in ioc/:

  • c2-ips.txt - Known command & control IP addresses
  • malicious-domains.txt - Payload hosting and exfiltration domains
  • file-hashes.txt - Known malicious file SHA-256 hashes
  • malicious-publishers.txt - Known malicious ClawHub publishers
  • malicious-skill-patterns.txt - Malicious skill naming patterns

Daily Automated Scan

Cron job at 06:00 UTC with Telegram alerts. Install:

crontab -l | { cat; echo "0 6 * * * $HOME/.openclaw/workspace/skills/<skill-dir>/scripts/daily-scan-cron.sh"; } | crontab -

Threat Coverage

Based on research from 40+ security sources including:

Installation

# From GitHub
git clone https://github.com/adibirzu/openclaw-security-monitor.git \
  ~/.openclaw/workspace/skills/<skill-dir>
chmod +x ~/.openclaw/workspace/skills/<skill-dir>/scripts/*.sh

The OpenClaw agent auto-discovers skills from ~/.openclaw/workspace/skills/ via SKILL.md frontmatter. After cloning, the /security-scan, /security-remediate, /security-dashboard, /security-network, and /security-setup-telegram commands will be available in the agent.

Source

git clone https://clawhub.ai/adibirzu/openclaw-security-monitorView on GitHub

Overview

Provides real-time security monitoring, threat scanning, and auto-remediation for OpenClaw deployments. It leverages ClawHavoc threat intelligence, daily automated 32-point scans, a web dashboard, and Telegram alerts to detect and block threats quickly.

How This Skill Works

The agent performs continuous monitoring and daily 32-point security scans via the security-scan workflow. When findings are detected, it can apply fixes using 32 per-check remediation scripts through the security-remediate command, with optional dry-run or auto-approve modes, and surfaces results in a web dashboard and Telegram alerts.

When to Use It

  • You deploy OpenClaw and need ongoing, real-time security visibility across components.
  • You require automated discovery of threats like C2, exfiltration attempts, and privilege abuse.
  • You want scan-driven remediation to reduce manual incident handling.
  • You rely on a web dashboard and Telegram alerts for quick incident notification and visibility.
  • You need to verify security posture before and after hardening changes with repeatable checks.

Quick Start

  1. Step 1: Ensure dependencies (bash and curl) are available and set up the skill directory (<skill-dir>).
  2. Step 2: Run a full security scan: bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/scan.sh
  3. Step 3: Review results on the web dashboard or via Telegram; to auto-fix, run: bash ~/.openclaw/workspace/skills/<skill-dir>/scripts/remediate.sh --yes

Best Practices

  • Run the daily 32-point security scan regularly and act on Telegram alerts.
  • Always test remediations with --dry-run before applying fixes.
  • Use --yes for auto-approval only when you’ve validated fixes as safe for your environment.
  • Review and rotate credentials and webhook endpoints implicated by findings.
  • Familiarize with the 32 check list (e.g., file permissions, exfiltration blocks, gateway hardening, sandbox config) to tailor hardening.

Example Use Cases

  • An OpenClaw deployment triggers a memory poisoning detection, prompting automated remediation and a post-remediation dashboard review.
  • Daily scans uncover a suspicious external download and blocked it via remediation scripts, tightening gateway settings.
  • Threat intel identifies known malicious publishers; alerts surface in Telegram and dashboard for rapid response.
  • A SOC team uses the process-tree view from the dashboard to isolate a compromised credential and revoke access.
  • On-call engineers receive Telegram alerts and use the remediation suite to apply fixes across 32 checks with a dry-run first.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers