T03 · Remote Payload Retrieval and Execution
- Location
install.sh:15- Finding
Unverified Remote Installer and Wallet Binary Are Downloaded and Executed
- Content
View full analysis
/dev/null 2>&1 || true fi echo "Downloading sandbox binary from $BINARY_URL ..." TMP_TARGET="${BINARY_TARGET}.download" curl -L -o "$TMP_TARGET" "$BINARY_URL" mv -f "$TMP_TARGET" "$BINARY_TARGET" chmod +x "$BINARY_TARGET" "$SCRIPT_DIR/claw-wallet.sh" start ``` The documented installation command executes a mutable remote script directly: ```bash curl -fsSL https://www.clawwallet.cc/skills/install.sh | bash ``` The upgrade path repeats the same behavior: ```bash CLAW_WALLET_BASE_URL="${CLAW_WALLET_BASE_URL:-https://www.clawwallet.cc/skills}" echo "Upgrading from ${CLAW_WALLET_BASE_URL}/install.sh ..." export CLAW_WALLET_SKIP_INIT=1 curl -fsSL "${CLAW_WALLET_BASE_URL}/install.sh" | bash ``` ### Technical Analysis The installation and upgrade processes trust the current contents served by `www.clawwallet.cc`. Neither the installer script nor the downloaded `clay-sandbox` executable is pinned to an immutable release, authenticated with a signing key, or checked against a trusted SHA-256 digest. TLS protects data i ...[truncated 2656 chars]- Remediation
View remediation
