T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:25- Finding
Unverified Remote Installer Executed Directly by a Shell
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a coherent external research integration, but it asks users to create recurring cron monitoring and uses unsafe mutable install instructions without enough scoping or cleanup.
Install only if you are comfortable sending research prompts and related context to Chonkie. Avoid putting secrets or regulated data in queries, store CHONKIE_API_KEY securely, prefer a pinned and verified chdr/Rust installation path, and do not create the suggested cron job unless you also define cleanup and explicitly approve the persistent scheduler change.
SKILL.md:25Unverified Remote Installer Executed Directly by a Shell
SKILL.md:24Unpinned Third-Party CLI Installation
SKILL.md:57Recurring Cron Job Recommended Without Lifecycle Cleanup
The skill instructs users to authenticate via browser login or by setting CHONKIE_API_KEY, but it gives no warning about safe credential handling, storage, or avoiding exposure in logs and shared environments. This can lead to accidental leakage of API secrets during setup or later command execution.
The core workflow sends user-supplied research queries and receives report content from an external service, but the skill does not clearly warn that prompts, embedded data, or sensitive business context will leave the local environment. This creates a real privacy and data-governance risk, especially for confidential or regulated information.
The skill explicitly recommends creating a cron job to monitor research status, which introduces persistent scheduled execution outside the core one-shot research task. Persistent jobs can outlive the user’s intent, create unnecessary background activity, and expand the operational footprint of the skill beyond what is needed.
The instruction to add a cron entry creates session persistence through recurring background execution, which is broader than necessary for checking a single research task. Such persistence can linger unnoticed, consume resources, and create an avenue for repeated external access or notifications beyond the original task scope.
Do NOT poll continuously for status. Instead, set up a cron job to check periodically (every 2-3 minutes):
# Add a cron entry to check research status every 2 minutes
# The cron should run: chdr view <id> --json | python3 -c "import json,sys; d=json.load(sys.stdin); s=d.get('status','unknown'); print(s)"
# and notify you when status is 'completed' or 'failed'
The setup path recommends piping a remote script directly into sh, which bypasses inspection and executes code fetched over the network immediately. Even with TLS, this pattern increases supply-chain risk because compromise of the remote source or transport path would lead to arbitrary code execution on the host.
Before using, check if `chdr` is installed (`which chdr`). If not:
1. Install: `cargo install chdr`
- If `cargo` isn't available, install Rust first: `curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh`
2. Authenticate: `chdr auth login` (opens browser to get an API key)
- Or set `CHONKIE_API_KEY` environment variable
- Get a key at https://labs.chonkie.ai/settings/api-keys
The manifest frames the skill as a way to run research and return comprehensive reports with citations. Advertising deletion of reports extends the skill into lifecycle management of remote research artifacts, which is not needed for the stated read/report use case.