T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:47- Finding
Unverified Remote Installer Is Executed Directly by a Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 47-56
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: CriticalVulnerable Code
bash # Linux — review first: https://github.com/zettabrain/zettabrain-rag/blob/main/install.sh curl -fsSL https://zettabrain.app/install.sh | sudo bash # macOS — review first: https://github.com/zettabrain/zettabrain-rag/blob/main/install.sh curl -fsSL https://zettabrain.app/install.sh | bash # Windows — review first: https://github.com/zettabrain/zettabrain-rag/blob/main/install.ps1 irm https://zettabrain.app/install.ps1 | iexTechnical Analysis
These commands retrieve mutable content from
zettabrain.appand immediately pass it to Bash or PowerShell. There is no version pinning, cryptographic checksum, signature verification, or opportunity to inspect the exact downloaded artifact before execution.The documentation links to installer source hosted on GitHub, but the executed payload is served from a different origin. Consequently, reviewing the GitHub file does not prove that
zettabrain.appwill return identical content. Redirects are also followed bycurl -L, increasing reliance on the integrity of the entire delivery chain.The Linux command is especially dangerous because it invokes the downloaded payload through
sudo bash, granting arbitrary root-level execution. The macOS and Windows variants execute with all permissions held by the current user.Attack Path
- An attacker compromises the installer hosting account, web server, DNS configuration, deployment process, or another component controlling
zettabrain.app. - The attacker replaces the installer response with a malicious shell or PowerShell script.
- A user follows the documented one-line installation command.
- The response is streamed directly into the interpreter without integrity verification.
- On Linux, the malicious payload execu ...[truncated 890 chars]
- An attacker compromises the installer hosting account, web server, DNS configuration, deployment process, or another component controlling
- Remediation
View remediation
Remediation Suggestions
- Remove all pipe-to-shell and
irm | iexinstallation instructions. - Distribute versioned, immutable release artifacts through a trusted release channel.
- Require users to download the installer to a local file before execution.
- Publish SHA-256 or stronger checksums and cryptographic signatures through an independently protected channel.
- Verify both the checksum and signature before executing the installer.
- Ensure that the reviewed source and downloaded artifact are demonstrably identical.
- Avoid executing the entire installer as root. Isolate necessary system changes in a small, separately audited privileged helper.
- Prefer the documented
pipxinstallation path for the user-level application.
- Remove all pipe-to-shell and
