T06 · System Persistence
- Location
SKILL.md:38- Finding
Persistent Scheduled and Boot-Time Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is purpose-aligned, but it deserves review because it can persistently modify an installed OpenClaw plugin and restart the Gateway automatically.
Install only if you intentionally want this skill to patch your local OpenClaw Feishu installation. Review the script first, run it manually before adding cron, be prepared for Gateway restarts, and avoid scheduled use unless the skill directory is protected and you have a recovery plan for the modified probe.ts file.
SKILL.md:38Persistent Scheduled and Boot-Time Execution
scripts/check-and-fix.js:16Unverified In-Place Modification of Installed OpenClaw Source
Importing and using execSync to restart a service gives the script a broader operational capability than its stated purpose of checking and fixing cache configuration. Even though the command string is static and not obviously injectable here, this still increases the blast radius of running the skill and can enable unintended service interruption when users expect only file inspection or modification.
The script performs an operationally significant side effect—restarting the OpenClaw Gateway—while presenting itself primarily as a cache-checking and repair tool. Hidden or underdocumented service restarts can cause unexpected downtime, disrupt active workloads, and make reviewers underestimate the privileges and impact of executing the skill.
The package description is written entirely in Chinese, which imposes a specific language choice in user-facing metadata without indicating any opt-in, alternative locale, or region-specific justification. This can violate language/locale policy when skills are expected to be accessible without forcing one language by default.
The header comment describes only checking and repairing probe.ts cache configuration, omitting that the script also restarts the Gateway. This kind of mismatch is dangerous because operators and code reviewers may approve or run the tool without realizing it can affect service availability, especially in automation contexts.