T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:80- Finding
Unverified Remote Installer Piped Directly to a Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 80
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code:
bash curl -fsSL https://tailscale.com/install.sh | shTechnical Analysis
The installation instructions download a mutable remote script and immediately pipe its contents to
sh. The payload is neither version-pinned nor verified using a cryptographic signature or trusted checksum, and the user has no opportunity to inspect it before execution.Although the URL uses HTTPS and appears to belong to Tailscale's official domain, those properties do not eliminate the risk. Compromise of the remote endpoint, its distribution infrastructure, DNS or TLS trust chain, or the installer publication process could cause arbitrary attacker-controlled commands to execute locally. The effective code can also change after the Skill itself has been reviewed.
Installing Tailscale is consistent with the Skill's declared VPN functionality. However, piping an unverified remote response directly into a shell exceeds what is necessary to perform that installation safely. Signed operating-system packages or a separately downloaded and verified installer can provide the same functionality with less supply-chain exposure.
Attack Path
- An attacker compromises or gains control over the installer endpoint or an upstream component capable of changing its response.
- The attacker modifies
https://tailscale.com/install.shto include arbitrary shell commands. - A user or agent follows the documented installation command.
curlretrieves the modified response and passes it directly tosh.- The malicious commands execute with the privileges of the user invoking the command.
- If the installer requests elevation or is run from a privileged shell, the payload may gain administrative or root-level access.
Impact Assessment
Successful exploitation permits ...[truncated 608 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | shpipeline. - Prefer the operating system's package manager and Tailscale's signed package repository, pinning an approved package version where operationally practical.
- If a standalone installer is required:
- Download it to a local file without executing it.
- Verify a publisher-provided cryptographic signature or a checksum obtained through an independently trusted channel.
- Review the downloaded script before execution.
- Execute it only after verification succeeds.
- Run installation with the least privileges possible and elevate only the specific package-management or service-management operation that requires it.
- Document the expected installer source, version, digest, required privileges, and resulting system changes so future audits can detect unexpected changes.
- Remove the direct
