T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:47- Finding
Remote installer is downloaded and executed without integrity verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 47
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Highbash bun --version || curl -fsSL https://bun.sh/install | bashTechnical Analysis
The setup instruction pipes content retrieved from
https://bun.sh/installdirectly intobash. The downloaded payload is not pinned to an immutable version, inspected before execution, or verified against an expected cryptographic digest or signature.Consequently, the code executed during installation can change after the Skill has been reviewed. HTTPS protects the connection in transit under normal circumstances, but it does not protect against compromise of the hosting service, DNS or certificate infrastructure, the upstream publishing account, or the installer itself.
Installing Bun is relevant to the documented setup process, but immediate execution of mutable remote content exceeds the minimum privilege necessary. A safer installation flow can download a fixed release artifact and verify it before execution.
Attack Path
- An attacker compromises the remote installer, its hosting infrastructure, or an authorized upstream publishing account.
- The attacker modifies the response served by
https://bun.sh/install. - A user or agent follows the Skill setup instructions on a host where Bun is unavailable.
- Because
bun --versionfails, the shell evaluates the right side of||. curlretrieves the attacker-controlled response and streams it directly intobash.- The payload executes with all permissions available to the user running the agent or setup command.
Impact Assessment
Successful exploitation permits arbitrary command execution in the invoking user's security context. The payload could read or alter user-accessible files, inspect environment variables and credentials, modify shell configuration, install additional executables, or access authenti ...[truncated 463 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashinstallation pattern. - Direct users to Bun's official installation documentation or a trusted operating-system package manager.
- If automated installation is required, pin an exact Bun release and download its immutable release artifact separately.
- Verify the artifact using a hardcoded SHA-256 digest or a valid upstream cryptographic signature before installation.
- Store the downloaded file temporarily, allow inspection, and execute it only after verification succeeds.
- Run installation with an unprivileged account and avoid requesting elevated permissions.
- Document the files and environment settings that installation will modify.
- Prefer failing with a clear prerequisite error when Bun is absent rather than automatically executing remote code.
- Remove the
