T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:77- Finding
Unverified Remote Installer Executed Directly Through Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 77
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code
bash curl -fsSL https://api.gtm-tools.sh/extension/install.sh | bashTechnical Analysis
The installation instructions download a mutable shell script from an external server and immediately execute it with Bash. The response is not inspected, pinned to a specific version, verified against a checksum, or authenticated through a cryptographic signature.
Although HTTPS protects the connection in transit, it does not ensure that the server-controlled script remains identical to the version considered during this audit. Compromise of the hosting server, deployment pipeline, domain, or maintainer account—or an intentional subsequent modification—could turn the endpoint into an arbitrary-code delivery mechanism.
The repository does not contain a reviewable copy of
install.sh; therefore, the installer's actual commands, filesystem effects, browser modifications, credential access, persistence behavior, and privilege requirements cannot be established from the audited artifact. Direct shell execution exceeds the minimum privilege required to provide extension-installation guidance. A pinned browser-store package or a downloaded and independently verified artifact would provide a narrower trust boundary.Attack Path
- A user or agent follows the instructions to connect a LinkedIn or Reddit browser session.
- The shell retrieves the current content served from
https://api.gtm-tools.sh/extension/install.sh. - The downloaded response is passed directly to Bash without validation or an opportunity for review.
- If the endpoint or its delivery infrastructure has been compromised, attacker-controlled commands execute with the privileges of the invoking user.
- Those commands could inspect or alter accessible files, environment variables, API configuration, or browser-related ...[truncated 921 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashpipeline. - Distribute the extension through a trusted browser extension store where possible, and link users to a fixed publisher identity.
- If a shell installer is necessary, publish immutable, versioned release artifacts rather than a mutable endpoint.
- Require users to download the installer separately and verify a pinned SHA-256 digest and a cryptographic signature before execution.
- Keep a reviewable copy of the installer in the repository or link to its exact source revision.
- Document all files, browser settings, network endpoints, and permissions modified by the installer.
- Ensure the installer runs without elevated privileges unless a narrowly defined operation genuinely requires them.
- Require explicit user confirmation before installation and before any permission-sensitive browser-session connection.
- Add reproducible release procedures and protect the signing and deployment pipelines with strong access controls.
- Provide uninstall and credential-revocation instructions for incident recovery.
- Remove the direct
