Security audit
Security checks for vulnerabilities and agentic risk
This skill coherently installs a disclosed OpenClaw startup hook that sends gateway-start notifications to a user-selected messaging channel.
Install only if you want a persistent OpenClaw hook that automatically sends gateway startup metadata to your configured messaging service. Review the generated config.json and handler.ts before restarting the gateway, and verify ~/.openclaw/hooks/gateway-notify before using the uninstall deletion command.
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
1. Create the hook directory at `~/.openclaw/hooks/gateway-notify`
2. Generate `HOOK.md` and `handler.ts` with your channel config
3. Enable the hook
4. Print instructions to restart the gateway
After restart, you'll receive a notification like:
The uninstall command uses rm -rf on a filesystem path, which is inherently risky because it irreversibly deletes content without confirmation. In this skill, the path is constrained to the hook's installation directory, so the context lowers severity, but it still presents a real chance of accidental deletion if users copy, edit, or run the command in the wrong environment.
openclaw hooks disable gateway-notify
rm -rf ~/.openclaw/hooks/gateway-notify
The uninstall command uses rm -rf on a filesystem path, which is inherently risky because it irreversibly deletes content without confirmation. In this skill, the path is constrained to the hook's installation directory, so the context lowers severity, but it still presents a real chance of accidental deletion if users copy, edit, or run the command in the wrong environment.
openclaw hooks disable gateway-notify
rm -rf ~/.openclaw/hooks/gateway-notify
The skill explicitly sends gateway startup details, including timestamp and local gateway address, to third-party messaging services but does not warn users that operational metadata will leave the host and be processed by external providers. This creates a real privacy and data-handling risk, especially for users who may not realize startup events and network details are being transmitted off-system.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
The script will:
1. Create the hook directory at `~/.openclaw/hooks/gateway-notify`
2. Generate `HOOK.md` and `handler.ts` with your channel config
3. Enable the hook
4. Print instructions to restart the gateway
The uninstall instructions include a recursive deletion command against a user directory without any warning to verify the path first. Although the target path is specific, destructive shell commands can cause accidental data loss if copied blindly, modified incorrectly, or expanded unexpectedly in edge cases.
The generated handler hard-codes toLocaleString("en-US", { hour12: false }), which imposes a specific locale in user-facing notification content. This is a natural-language/locale policy issue because the skill does not offer a language or locale choice, nor document why a U.S. English format is required.
Detected: suspicious.destructive_delete_command