T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:16- 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’s product-image workflow is coherent, but its setup instructions execute a live remote installer and recommend unpinned optional skill installs.
Review this before installing. Prefer a manually downloaded, version-pinned `infsh` release with an independently verified checksum or signature, and avoid the `curl | sh` and unpinned `npx skills add` commands unless you trust those publishers and registries. Use a least-privileged environment and do not log in with production credentials unless you accept the external service’s data handling.
SKILL.md:16Unverified Remote Installer Executed Directly by a Shell
SKILL.md:247Unpinned Third-Party Package and Skill Installation Commands
Piping a remotely fetched script directly into sh executes network-supplied code immediately, creating a classic arbitrary code execution and supply-chain compromise risk. Even though the document claims checksum verification and benign installer behavior, users cannot safely validate those assurances before execution because the fetched script itself is what gets executed first.
curl -fsSL https://cli.inference.sh | sh && infsh login
# Generate product shot
infsh app run falai/flux-dev --input '{
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.
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.
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.
No suspicious patterns detected.