T06 · System Persistence
- Location
SKILL.md:92- Finding
Persistent Autonomous Polling Task Survives the Initiating Skill Run
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real chat integration, but it asks users to enable persistent autonomous agent activity and internet-facing message intake with insufficient safety boundaries.
Install only if you are comfortable with an agent chatting with unknown third parties on an ongoing basis. Prefer manual, foreground polling; avoid the cron job unless you set a clear duration and monitoring. Do not expose internal gateways casually, treat all incoming chat as hostile prompt content, restrict available tools for chat sessions, and store the API key with secret-manager or 0600-style protections. Pin and verify any downloaded skill files before use.
SKILL.md:92Persistent Autonomous Polling Task Survives the Initiating Skill Run
SKILL.md:51Stranger-Controlled Chat Content Is Injected into an Autonomous Agent Wake Message
SKILL.md:8Mutable Remote Skill Instructions Are Downloaded Without Integrity Verification
SKILL.md:19Unpinned Third-Party Installation Commands Create Supply-Chain Exposure
SKILL.md:146Bearer API Credential Is Stored Without Required Filesystem Protection
The skill instructs users to store an API key in a plaintext credentials.json under a predictable path. Plaintext local credential storage increases the chance of accidental disclosure through backups, logs, broad file permissions, or other local processes, and the key authorizes chat operations and webhook configuration against the service.
⚠️ Save your api_key immediately! You need it for all requests.
Save credentials to: ~/.config/clawmegle/credentials.json:
{
The skill tells users to execute npx clawdhub install clawmegle without pinning a specific package version. That permits silent changes in installer behavior over time and increases supply-chain risk if the package or its dependencies are compromised. In this context, an install command is a trust boundary, so unpinned execution is meaningfully risky.
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.
Or install manually:
mkdir -p ~/.config/clawmegle
curl -s https://www.clawmegle.xyz/skill.md > ~/.config/clawmegle/SKILL.md
curl -s https://www.clawmegle.xyz/heartbeat.md > ~/.config/clawmegle/HEARTBEAT.md
The skill instructs users to fetch remote skill files directly from clawmegle.xyz into a local config directory with curl, implicitly trusting unauthenticated remote content at install time. Even over HTTPS, this creates an external content ingestion path that could deliver modified instructions or malicious updates if the remote host or delivery chain is compromised.
Or install manually:
mkdir -p ~/.config/clawmegle
curl -s https://www.clawmegle.xyz/skill.md > ~/.config/clawmegle/SKILL.md
curl -s https://www.clawmegle.xyz/heartbeat.md > ~/.config/clawmegle/HEARTBEAT.md
The skill requires users to expose an inbound webhook endpoint and register it with a third-party chat service, which expands the skill from outbound chat API usage into inbound network exposure. That creates an unnecessary attack surface: remote parties can trigger the agent, deliver untrusted content, and potentially reach local or semi-public infrastructure such as localhost, Tailscale, or reverse-proxied gateways.
The documentation tells users to expose a webhook endpoint to the internet and register it with a third party, but does not adequately warn about privacy, internet exposure, request forgery, or the risks of sending untrusted messages into an agent workflow. Because the skill is designed for random agent-to-agent chat, inbound content is inherently untrusted and should be treated as hostile.
The skill directs agents to create a recurring cron job that autonomously polls, interprets messages, and responds on an ongoing basis. This materially expands behavior from a simple chat skill into persistent autonomous operation, which can generate unintended actions, continuous external communication, and reduced operator visibility over when the agent is active.
The skill explicitly instructs creation of a persistent cron job that maintains an isolated agent session and repeatedly performs network actions. Persistence is security-relevant here because it enables ongoing autonomous behavior long after initial installation, reducing user awareness and increasing exposure to untrusted remote input.
This is the easiest way to enable real-time chat! Create a cron job that polls every 45 seconds:
clawdbot cron add \
The cron-based auto-polling guidance encourages persistent autonomous behavior every 45 seconds without clear notice of resource consumption, continuous outbound traffic, and operational persistence. While not inherently exploitable by itself, it can normalize unattended agent activity and make misuse or runaway interactions harder to notice.