T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:16- Finding
Unverified Remote Installer Executed Directly in a Shell
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is for image upscaling, but its setup instructions ask users to run mutable remote installer and package-install commands that should be reviewed before use.
Review the installer and any related skills before running them. Prefer a pinned, manually downloaded, checksum-verified CLI install path, run login separately, and avoid the optional npx skill-add commands unless you trust and have reviewed those packages.
SKILL.md:16Unverified Remote Installer Executed Directly in a Shell
SKILL.md:62Mutable Third-Party Skill Dependencies Installed Through npx
curl -fsSL https://cli.inference.sh | sh pipes a remotely fetched script directly into a shell, enabling arbitrary code execution if the server, CDN, DNS, TLS trust chain, or publishing pipeline is compromised. Although the surrounding text claims checksum verification and no elevated permissions, those assurances are themselves untrusted documentation and do not remove the core risk of executing a mutable remote script.
curl -fsSL https://cli.inference.sh | sh && infsh login
infsh app run infsh/real-esrgan --input '{"image_url": "https://your-image.jpg"}'
The trigger list includes broad phrases such as enhance image, higher resolution, and image enhancement, which are common user intents and can cause the skill to activate unexpectedly. Over-broad invocation increases the chance that users are steered into running the skill's shell-based workflows, including remote install commands, in contexts where they did not explicitly request this tool.
The skill recommends executing npx skills add ... without pinning an exact package version, which allows retrieval of whatever version is current at execution time. If the upstream package is compromised or a breaking/malicious release is published, users may install and run unreviewed code.
This npx skills add ... command is unpinned, so it resolves to the latest published package at runtime rather than a reviewed version. That creates a software supply-chain risk: future package compromise or namespace abuse could lead to arbitrary code execution on the user's machine.
The example uses npx skills without version pinning, making execution dependent on the current registry state. In documentation intended for end users, this is dangerous because it normalizes running mutable remote package code directly from the package registry.
An unpinned npx skills add ... command introduces a supply-chain risk because users cannot know in advance which package contents will be executed. In the context of a skill file that may be copied verbatim, this can directly expose users to malicious package updates.
No suspicious patterns detected.