Back to skill

Security audit

orchestration, telegram, cron

Security checks across malware telemetry and agentic risk

Overview

The skill is coherent and not malicious, but it gives Telegram chat commands high-impact control over skill installation and scheduled agent jobs without enough built-in safeguards.

Install only in a tightly controlled private setup. Before using it for real operations, add enforcement of Telegram chat.id and from.id in the executable path, restrict allowed skill publishers or slugs, require human approval for installs and cron changes, default new cron jobs to disabled or expiring, and keep the Dev bot token in protected configuration.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Taint TrackingDirect Taint Flow, Variable-Mediated Taint Flow, Credential Exfiltration Chain
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (3)

Tainted flow: 'tmp' from os.environ.get (line 179, credential/environment) → open (file write)

Medium
Category
Data Flow
Content
# Use openclaw cron add via stdin json (if supported) else via temp file.
        # We'll write a temp file.
        tmp = os.path.join(ws, "tmp-cron-job.json")
        with open(tmp, "w", encoding="utf-8") as f:
            json.dump(job, f)
        rc, out = run(["openclaw", "cron", "add", "--file", tmp], cwd=ws)
        try:
Confidence
82% confidence
Finding
with open(tmp, "w", encoding="utf-8") as f:

Lp3

Medium
Category
MCP Least Privilege
Confidence
92% confidence
Finding
The skill instructs the Dev bot to execute local CLI actions that inherently require shell, file, and environment access, yet it declares no permissions or trust boundaries. In this context, the bot is explicitly designed to install skills and manage cron jobs based on Telegram messages, so undeclared capabilities hide a meaningful remote-control surface and can lead to unexpected command execution or persistent task creation if misconfigured.

Intent-Code Divergence

High
Confidence
99% confidence
Finding
The module claims it will only accept commands from a specific Telegram group and PM identity, but the implemented command-processing path never validates sender or group metadata at all. In the context of a bot meant to install skills and add, run, enable, or remove cron jobs on a Dev server, missing authorization is highly dangerous because any forwarded or injected command text could trigger privileged local actions.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.