T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:72- Finding
Unverified Remote Installer Scripts Executed Directly from the Network
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 72–76
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
The installation instructions retrieve scripts from external URLs and immediately execute their contents through Bash or PowerShell. The scripts are not pinned to an immutable version, downloaded for inspection, authenticated with a cryptographic signature, or checked against an expected digest.
TLS protects the network connection in transit but does not ensure that the remote script remains unchanged after the Skill has been reviewed. Compromise of the hosting infrastructure, DNS or certificate ecosystem, deployment process, or upstream maintainer account could therefore turn these commands into an arbitrary-code execution channel.
This behavior also exceeds the minimum runtime privileges declared by the Skill. Its declared tool access is limited to
Bash(oo *), while installation executes arbitrary instructions supplied by a remote server rather than an existingoocommand. Although installation is presented as a fallback for a missing CLI rather than routine behavior, that condition still provides a documented path to execute mutable external code.The ordinary connector network traffic is necessary for the declared Sage Sales Management integration, and the audited file contains no evidence of covert credential collection or transmission to an unrelated destination. The security issue is specifically the unverified execution of installer payloads.
Attack Path
- The
ooCLI is unavailable on the host, causing an agent or user to follow the first-time setup instructions. - The command requests the current installer from
cli.oomol.com.
...[truncated 1097 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove all pipe-to-shell and
Invoke-Expressioninstallation commands from the Skill instructions. - Keep tool installation outside automated Skill execution and require the CLI to be installed through a separately reviewed administrative process.
- Prefer an official operating-system package manager or a version-pinned release artifact from a documented publisher.
- Pin downloads to an immutable release version rather than a mutable
install.shorinstall.ps1endpoint. - Publish an expected SHA-256 or stronger digest and verify it before execution. Prefer signed artifacts and validate signatures against a documented, trusted signing key.
- Download the installer to a local file, inspect or review it, verify its integrity, and only then execute it as a separate command.
- Document the exact files, directories, environment changes, network endpoints, and privileges required by installation.
- Run installation with the least-privileged account possible and avoid requesting administrative elevation unless a specific, documented operation requires it.
- Preserve the existing runtime restriction to
oocommands and ensure fallback setup instructions cannot be interpreted as authorization to execute arbitrary shell content.
- Remove all pipe-to-shell and
