T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:16- Finding
Unaudited Remote Installer Executed Directly by Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 16
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighComplete Code Snippet:
bash curl -sSL https://trust-audit-framework.vercel.app/api/agent/install | bashTechnical Analysis
The documented installation command downloads shell content from a live API endpoint and immediately executes it with
bash. The project contains no local implementation, pinned release, checksum, cryptographic signature, or inspectable installer. The effective payload can therefore change after the Skill has been reviewed.HTTPS protects data in transit but does not guarantee that the server will always return the audited payload. Compromise of the remote service, its deployment account, DNS or hosting infrastructure—or intentional modification by its operator—could cause arbitrary shell commands to be returned and executed.
This installation mechanism is not necessary for the declared reputation and attestation functionality. It grants mutable remote content all permissions held by the invoking user and therefore does not satisfy least-privilege principles.
Attack Path
- A user or autonomous agent follows the installation command in
SKILL.md. - The external endpoint is compromised or intentionally changed to return malicious shell code.
curlretrieves the malicious response without saving it for inspection.- The pipe sends the response directly to
bash. - Bash executes the payload with the invoking user's permissions.
- The payload can access user-readable data, modify user-writable files, execute additional programs, or establish persistence where existing permissions allow it.
Impact Assessment
Successful exploitation provides arbitrary command execution under the invoking user's account. This may expose credentials, configuration files, source code, agent state, and other user-accessible data. It may also ...[truncated 609 chars]
- A user or autonomous agent follows the installation command in
- Remediation
View remediation
Remediation Suggestions
- Replace the
curl | bashpipeline with a versioned installer artifact hosted in a verifiable release repository. - Pin the installer to an immutable version or commit rather than a mutable API endpoint.
- Publish the complete installer source so users and auditors can inspect its behavior.
- Provide a documented SHA-256 digest and verify it before execution.
- Cryptographically sign release artifacts and document signature verification using a pinned, independently distributed public key.
- Separate download, verification, inspection, and execution into distinct commands.
- Avoid requiring administrator privileges; explicitly document the files, network access, and permissions needed.
- Ensure installation is confined to a dedicated directory and does not create startup services, scheduled tasks, or other persistence without explicit informed consent.
- Vendor the implementation in the Skill package where practical so its behavior can be reviewed statically.
- Replace the
