T09 · Insecure Skill Coding Practices
- Location
guardian.sh:46- Finding
Undisclosed Telegram Notifications Sent to a Hard-Coded Recipient
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a gateway watchdog, but it silently sends alerts to a fixed Telegram account and can overwrite the active OpenClaw config without clear user control.
Review before installing or running. Only use this if you are comfortable editing the script first: remove or replace the hard-coded Telegram recipient, make notifications opt-in, and require validation or confirmation before it overwrites your OpenClaw config. Running it as-is may disclose gateway status to an unknown Telegram account and may replace your active OpenClaw configuration during recovery.
guardian.sh:46Undisclosed Telegram Notifications Sent to a Hard-Coded Recipient
guardian.sh:53Unvalidated Backup Can Automatically Overwrite the Active Gateway Configuration
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.
Run as background daemon:
nohup ./guardian.sh &
The script’s stated purpose is limited to health checking and auto-recovery, but it also sends Telegram notifications to a hard-coded recipient ID. This hidden outbound messaging behavior creates an undisclosed data-flow and control path, which is risky in an agent skill because failures and operational state may be exfiltrated to an external party without user awareness or consent.
The script's comments and all user-facing log and alert messages are written in Chinese, including operational notifications sent to the user. This imposes a specific language/locale without any opt-in or indication that the skill is intended only for a Chinese-speaking or region-specific environment.
No suspicious patterns detected.