T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:31- Finding
Mutable Remote Shell Script Is Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 31-33
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code:
bash curl -fsSL https://raw.githubusercontent.com/holon-run/uxc/main/scripts/install.sh -o install-uxc.sh less install-uxc.sh bash install-uxc.shTechnical Analysis
The installation instructions download a shell script from the mutable
mainbranch of an external GitHub repository and then execute it with Bash. The URL is not pinned to an immutable commit, and the downloaded file is not authenticated through a cryptographic signature or verified against a trusted checksum.Although the instructions recommend reviewing the file with
less, this is a manual safeguard and does not enforce verification. The upstream script can change after this Skill has been reviewed. Compromise of the upstream repository, maintainer account, release process, DNS or network trust chain could therefore change the effective code executed by users without requiring any modification to this project.Retrieving documentation through DeepWiki requires network access, but executing mutable third-party installation code is not the minimum privilege necessary for the Skill's core query functionality. It is an optional setup mechanism that materially expands the supply-chain attack surface.
Attack Path
- An attacker compromises the upstream
holon-run/uxcrepository, a maintainer account, or the process that publishesscripts/install.sh. - The attacker modifies the installer on the mutable
mainbranch to contain malicious shell commands. - A user follows the installation instructions in
SKILL.md. curldownloads the attacker-controlled version asinstall-uxc.sh.- The user runs
bash install-uxc.sh. - The malicious commands execute with the privileges and environment of the invoking user.
Impact Assessment
The downloaded script re ...[truncated 574 chars]
- An attacker compromises the upstream
- Remediation
View remediation
Remediation Suggestions
- Remove the remote shell-script installation method and prefer a trusted package manager with a pinned, reviewed release.
- If a script installer must remain available, pin its URL to a specific immutable Git commit rather than
main. - Publish the expected SHA-256 digest through an independently trusted release channel and verify it before execution.
- Prefer cryptographic signature verification using a documented maintainer signing key.
- Fail closed when verification fails; do not present manual visual inspection as the primary integrity control.
- Document the installer's expected filesystem changes, network destinations, and privilege requirements.
- Recommend installation in an isolated environment or unprivileged user context and explicitly warn users not to execute it with
sudo.
