LobsterGuard

• Risk level: Low
• Analyzed: Feb 25, 2026, 1:09 PM
• Findings: 0
• Version: 6.1.0

Overview

LobsterGuard broadly fits its stated role (local security auditor + shield) but contains behaviors and implementation details that increase risk (persistent system services, privileged auto-fixes, and unsafe shell invocation patterns that could allow command injection); review and run only in an isolated environment after code review.

What to consider before installing LobsterGuard: - Review the code first: inspect install.sh, scripts/fix_engine.py, scripts/check.py, and any systemd unit files to confirm exactly what will run as your user or under sudo. Pay particular attention to how arguments are passed to shell commands. - Run in isolation: install and test the skill inside a non-privileged container or VM (the SKILL.md even contains a Docker guide). Do not install directly on a production host until you’re comfortable. - Limit privileges: avoid giving sudo or system-wide install rights until you trust the code. Auto-fixes require sudo; prefer manual guidance for the first runs. - Use a dedicated Telegram bot/token: the TELEGRAM_BOT_TOKEN is sensitive. Create a bot limited to receiving messages (no other integrations) and use a chat dedicated to alerts. - Check for command-injection risk: the extension builds shell command strings from parameters (e.g., check_id, target_user). If you plan to allow autonomous invocation, ensure input is sanitized or run only in environments where those parameters are controlled. - Confirm persistence and roll-back: the installer adds systemd services and an OpenClaw extension. Ensure you can fully remove these (and test rollback) before granting permanent installation. If you are not comfortable auditing the code yourself, prefer running LobsterGuard only in an isolated environment and avoid granting sudo/system-wide installs until a trusted reviewer signs off.