T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:26- Finding
Unverified Remote Installation Script Executed Directly by Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:26-31; duplicated inREADME.md:33-37
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable code in
SKILL.md:markdown - `novitaclaw` CLI must be installed. If not found: `curl -fsSL https://novitaclaw.novita.ai/install.sh | bash` - `novita-sandbox` npm package must be available. If not: `npm install novita-sandbox`Vulnerable code in
README.md:markdown - **novitaclaw CLI** — install with: ```bash curl -fsSL https://novitaclaw.novita.ai/install.sh | bash ```Technical Analysis
The documented installation procedure downloads mutable content from an external URL and pipes it directly into Bash. The payload is executed without first saving it for inspection and without a pinned version, checksum, digital signature, or other integrity verification.
Consequently, the code that users execute can differ from the code reviewed during this audit. HTTPS protects transport under normal conditions but does not protect against compromise of the hosting service, publisher account, DNS or certificate infrastructure, or an intentional future replacement of the script.
Direct remote execution is not the minimum privilege necessary to install the required CLI. A versioned artifact can instead be downloaded, authenticated, inspected, and installed using narrowly scoped permissions.
Attack Path
- An attacker compromises the script host, deployment pipeline, publisher credentials, or another component controlling
https://novitaclaw.novita.ai/install.sh. - The attacker replaces the installation script with a malicious shell payload.
- A user or Agent follows the prerequisite instructions.
curlretrieves the current attacker-controlled response.- The pipe passes that response directly to Bash without validation.
- The payload executes with all permissions available to t ...[truncated 444 chars]
- An attacker compromises the script host, deployment pipeline, publisher credentials, or another component controlling
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashinstallation instruction from both documentation files. - Publish versioned release artifacts through a trusted release channel.
- Pin an explicit release version rather than retrieving a mutable endpoint.
- Download the artifact to disk without executing it immediately.
- Verify a publisher signature or a checksum obtained through an independently authenticated channel.
- Provide users with an opportunity to inspect the downloaded script before execution.
- Avoid requiring administrator privileges unless a specific installation step genuinely needs them.
- Document the files, directories, and environment changes performed by the installer.
- If a package-manager installation is available, prefer a signed and versioned package from a trusted repository.
- Remove the
