T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:14- 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 a coherent case-study writing aid, but it asks users to run mutable remote installation commands and send research queries through external services.
Review before installing. Avoid running the pipe-to-shell installer as written; prefer a pinned release, signature or checksum verification before execution, and inspect any installer first. Do not send customer names, confidential metrics, deal details, or unreleased strategy to external search or executor apps unless you have permission.
SKILL.md:14Unverified Remote Installer Executed Directly by a Shell
SKILL.md:230Mutable and Unverified Third-Party Skill Installation Commands
curl -fsSL https://cli.inference.sh | sh executes a remotely fetched script directly in the user's shell, creating a classic supply-chain and remote code execution risk. Even with a later note about checksum verification, the one-line install encourages users to run unreviewed network content before any independent validation.
curl -fsSL https://cli.inference.sh | sh && infsh login
# Research the customer's industry
infsh app run tavily/search-assistant --input '{
The trigger list is broad enough to match ordinary terms like 'case study', 'use case', or 'customer story', which can cause the skill to activate in contexts where the user did not intend external research or tool use. In an agent environment, over-broad activation increases the chance of unnecessary data sharing or unexpected execution paths.
The research examples send business queries to third-party services (tavily/search-assistant, later also Exa) without warning that customer names, internal metrics, or strategic context could be transmitted externally. In a case-study workflow, prompts are especially likely to contain confidential client information, making silent exfiltration of business-sensitive data a realistic risk.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The embedded Python example saves an output file ("results-chart.png") to the local environment, which is a file write affecting user workspace contents. The surrounding documentation does not explicitly warn that running the example will create or overwrite a local file.
No suspicious patterns detected.