T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:20- Finding
Unverified Remote Installation Script Executed Through Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 20
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalComplete Code Snippet:
bash # One-click installation (recommended) curl -fsSL https://raw.githubusercontent.com/riba2534/feishu-cli/main/install.sh | bashTechnical Analysis
The recommended installation command downloads a shell script from a personal GitHub repository and pipes the response directly into
bash. The URL references the mutablemainbranch rather than an immutable commit or verified release. Consequently, the executed payload can change after the Skill has been audited.No cryptographic checksum, digital signature, pinned revision, or inspection step is required before execution. Although HTTPS protects the connection in transit, it does not establish that future repository content is safe. Compromise of the maintainer account or repository, or a malicious upstream modification, could therefore turn this command into arbitrary code execution.
This behavior is not necessary at the privilege level shown. The declared Feishu functionality requires a CLI, but it does not require executing an unreviewed remote response directly. A pinned and integrity-verified release artifact would satisfy the same functional requirement with substantially less supply-chain risk.
Attack Path
- An Agent activates the Skill for a Feishu-related task.
- The user or Agent follows the documented, recommended installation command.
- An attacker compromises the upstream repository or maintainer account, or otherwise causes malicious content to be served from the referenced mutable branch.
curlretrieves the modifiedinstall.shresponse.- The shell pipe passes that response directly to
bashwithout local review or integrity verification. - The malicious script executes arbitrary commands with the permissions of the invoking account.
- The pay ...[truncated 1090 chars]
- Remediation
View remediation
Remediation Suggestions
-
Remove the direct
curl | bashinstallation path. -
Pin installation assets to a reviewed version and immutable commit or release.
-
Publish SHA-256 checksums or cryptographic signatures through a trusted channel and verify them before execution.
-
Download the installer to a local file, validate its integrity, and permit inspection before running it.
-
Prefer an official package registry or a verified, organization-controlled distribution source.
-
Run installation without administrative privileges unless a documented installation step strictly requires them.
-
Do not expose Feishu secrets to the installer process. Configure credentials only after installation and verification.
-
Document the minimum Feishu API scopes required for each command and recommend separate, least-privilege credentials.
-
Provide reproducible build information or source-to-binary provenance for downloaded executables.
-
Replace the command with an integrity-verifying workflow, for example:
bash curl -fL -o feishu-cli.tar.gz \ "https://github.com/riba2534/feishu-cli/releases/download/<PINNED_VERSION>/<PLATFORM_ARCHIVE>" echo "<PUBLISHED_SHA256> feishu-cli.tar.gz" | sha256sum --check -Extraction and installation should occur only after checksum or signature validation succeeds.
-
