T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:26- Finding
Unverified Remote Installer Is Downloaded and Executed by Bash
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill's video-search purpose is clear, but it tells agents to run an unverified remote installer and persist an API key on disk in a way users should review first.
Review this skill before installing. Prefer a pinned, verifiable Cerul CLI installation method, avoid running the curl-to-bash installer automatically, and use a session-scoped or platform-managed CERUL_API_KEY instead of letting the agent print or persist the key in ~/.config/cerul/credentials.
SKILL.md:26Unverified Remote Installer Is Downloaded and Executed by Bash
SKILL.md:46API Credential Is Printed into Agent Output and Mandatorily Persisted in Plaintext
The skill metadata includes a shell install command that pipes a remotely fetched script directly into bash. This executes unverified code from the network at runtime, creating a supply-chain and remote code execution risk if the endpoint, transport, or script content is compromised.
homepage: https://github.com/cerul-ai/cerul
install:
- kind: shell
command: "curl -fsSL https://cli.cerul.ai/install.sh | bash"
bin: cerul
allowed-tools: Bash(cerul *)
---
The operational instructions tell the agent to install the CLI by fetching an external script and executing it immediately with bash. In an agent context, this is especially risky because it normalizes autonomous execution of remote code before performing the user's requested task.
If cerul is not found on PATH, install it first:
curl -fsSL https://cli.cerul.ai/install.sh | bash
Then check if the credentials file exists:
The use of '| bash' chains network retrieval directly into code execution with no inspection or integrity validation. This pattern is dangerous because it compresses download and execution into one step, making compromise or tampering immediately exploitable.
If cerul is not found on PATH, install it first:
curl -fsSL https://cli.cerul.ai/install.sh | bash
Then check if the credentials file exists:
The metadata declares CERUL_API_KEY as the primary environment variable, but the body forbids that safer session-scoped mechanism and mandates writing credentials to disk instead. This inconsistency can bypass platform secret-handling expectations and push the agent toward a less secure storage path.
The skill explicitly instructs the agent to ask for the user's API key and persist it in a long-lived file for future sessions, which exceeds what is necessary to answer a single video-search request. Persisting secrets on disk increases the chance of unintended reuse, disclosure to other tools/processes, or compromise from later filesystem access.
The skill tells the agent to save the user's API key in ~/.config/cerul/credentials without any warning about persistence, local exposure, or future-session reuse. Users may provide a secret without understanding it will be stored on disk beyond the immediate task.
These instructions direct the agent to request the API key from the user, write it to a config file, and keep it available across future sessions. That creates durable secret retention not required by the skill's core video-search function and expands the blast radius if the host is later accessed by other agents, users, or malware.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
If the file is empty or missing, ask the user for their API key (get one at https://cerul.ai/dashboard), then save it directly to the config file:
mkdir -p ~/.config/cerul && echo -n "cerul_XXXXX" > ~/.config/cerul/credentials && chmod 600 ~/.config/cerul/credentials
Do NOT use export CERUL_API_KEY=... — that only lasts for the current session. Always persist the key to ~/.config/cerul/credentials so it works across all future sessions and terminal windows.
The command creates a persistent credentials file and the text explicitly says this is so the key works across future sessions and terminal windows. That is unnecessary retention of a user secret and can enable unauthorized reuse long after the original request is complete.
If the file is empty or missing, ask the user for their API key (get one at https://cerul.ai/dashboard), then save it directly to the config file:
mkdir -p ~/.config/cerul && echo -n "cerul_XXXXX" > ~/.config/cerul/credentials && chmod 600 ~/.config/cerul/credentials
Do NOT use export CERUL_API_KEY=... — that only lasts for the current session. Always persist the key to ~/.config/cerul/credentials so it works across all future sessions and terminal windows.