T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:14- Finding
Unverified Remote Installation Script Executed Directly by a Shell
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is mostly a landing-page design guide, but its setup instructions ask users to run mutable remote installers and unpinned skill installs that deserve review before use.
Review this before installing. The design advice itself is ordinary, but do not run the curl-to-sh installer or unpinned npx skill commands unless you trust the publisher and have verified the downloaded artifacts through a safer, pinned or checksum/signature-based process. Treat infsh prompts, generated assets, and search queries as data sent to external services.
SKILL.md:14Unverified Remote Installation Script Executed Directly by a Shell
SKILL.md:238Unpinned Third-Party Skill Installation Through Dynamic Package Tooling
curl -fsSL https://cli.inference.sh | sh pipes remote content directly into a shell, which is a classic arbitrary code execution pattern. Even with claims about checksum verification, the bootstrap script itself is executed before independent verification by the user, so compromise of the host, CDN, DNS, TLS termination, or script publishing pipeline could lead to immediate code execution.
curl -fsSL https://cli.inference.sh | sh && infsh login
# Generate a hero image
infsh app run falai/flux-dev-lora --input '{
The manifest description lists triggers such as "landing page," "hero section," and especially "product page design," which are common design phrases and not narrowly scoped invocation conditions. The file does not provide constraints, exclusions, or negative examples clarifying when the skill should or should not activate.
Granting broad Bash access (Bash(infsh *)) is more permission than a content/design guidance skill should generally require. Even if partially scoped to infsh, it still authorizes command execution paths that can reach external services and potentially process sensitive user data or trigger unintended actions.
The manifest describes a skill for landing page conversion optimization, layout rules, CTA psychology, and related design guidance. In the file, the skill also instructs users to install an external CLI, generate images with remote models, and research competitor pages through external search services, which goes beyond the narrow design-guidance description in the manifest.
The skill recommends invoking npx skills add ... without pinning an exact package/version, which allows whatever the current published package resolves to at execution time. If the upstream package, dependency chain, or package owner is compromised, users may execute unexpected code during install/use.
This npx skills add ... reference is unpinned, so it depends on the latest registry state rather than a reviewed artifact. That creates a supply-chain risk where a malicious or compromised release could run code in the user's environment.
An unversioned npx install/use path is a real supply-chain exposure because package contents can change after the documentation is written. In a skill context, users may copy-paste the command directly, increasing the chance of executing unreviewed code.
No suspicious patterns detected.