T03 · Remote Payload Retrieval and Execution
- Location
scripts/install.sh:4- Finding
Unverified Remote Binary Download and Execution
- Content
View full analysis
&2 echo "${INSTALL_DIR}/autobahn" exit 0 fi echo "Downloading autobahn ${VERSION} for ${OS}-${ARCH_SUFFIX}..." >&2 mkdir -p "$INSTALL_DIR" if command -v curl >/dev/null 2>&1; then curl -fsSL -o "${INSTALL_DIR}/autobahn" "$URL" elif command -v wget >/dev/null 2>&1; then wget -q -O "${INSTALL_DIR}/autobahn" "$URL" else echo "Neither curl nor wget found" >&2 exit 1 fi chmod +x "${INSTALL_DIR}/autobahn" echo "$VERSION" > "$VERSION_FILE" echo "Installed autobahn ${VERSION} to ${INSTALL_DIR}/autobahn" >&2 echo "${INSTALL_DIR}/autobahn" ``` The downloaded executable is then explicitly required by the Skill: ```bash AUTOBAHN_BIN=$(bash ./scripts/install.sh) ``` ### Technical Analysis The installer retrieves a native executable from an external GitHub release repository and immediately marks it executable. It does not verify a cryptographic checksum, detached signature, Sigstore identity, provenance attestation, or immutable artifact digest. HTTPS protects the transport connection but does not establish that the release asset itself is the artifact reviewed by the auditor. The effective code executed by the Skill can therefore change after the p ...[truncated 2255 chars]- Remediation
View remediation
