Back to skill

Security audit

OpenRouter Cron Migration

Security checks for vulnerabilities and agentic risk

Overview

The skill has a clear OpenRouter cron-migration purpose, but it needs review because its instructions can expose API keys while changing scheduled jobs.

Install only if you are comfortable letting an agent inspect OpenClaw cron configuration, edit selected cron jobs, and run them for verification. Before using it, require secret-safe behavior: confirm only whether OpenRouter credentials exist, do not print ~/.openclaw/.env or auth profile contents, and use a secure secret entry method instead of pasting API keys into chat.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill explicitly instructs the operator to locate, verify, and use an OpenRouter API key from local files and environment state, and even asks the user to supply the key if missing. That creates unnecessary exposure of sensitive credentials in terminal output, chat history, shell history, and downstream tooling without any safety guidance to avoid printing, echoing, or persisting the secret.

Static analysis

No suspicious patterns detected.