T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:62- Finding
Unverified Remote Installer Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 62–66
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable 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 first-time setup instructions pipe remotely retrieved content directly into a command interpreter. The effective code is not included in the reviewed Skill package and can change after the Skill has been audited. Neither command pins an installer version nor verifies a cryptographic signature or checksum before execution.
Although the download host is consistent with the named OOMOL service and installation is presented as a fallback when the
oocommand is unavailable, executing an installer is not required for routine ChaserHQ read operations when the CLI is already installed. Installation also has substantially broader effects than invoking the narrowly allowedooconnector commands. Consequently, these instructions exceed the minimum runtime privileges needed for the Skill's declared read-only functionality.If the hosting infrastructure, installer publication process, DNS resolution, TLS trust chain, or vendor account is compromised, the downloaded response can contain arbitrary shell or PowerShell commands. The commands would execute with the privileges of the user or agent following the instructions.
Attack Path
- The
ooCLI is unavailable, causing the first-time setup fallback to apply. - The user or agent runs the documented installation command.
curlorInvoke-RestMethodretrieves a mutable script from the external OOMOL endpoint.- The response is passed directly to Bash or PowerShell without local inspection, version pinning, checksum validation, or signature verification.
- If the remote response has been maliciou ...[truncated 1095 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove both pipe-to-interpreter installation commands from the Skill instructions.
- Direct users to an authenticated official package repository or a specific, immutable release artifact.
- Pin the CLI to a reviewed version rather than downloading a mutable installation endpoint.
- Download the installer or package to disk without executing it automatically.
- Publish and verify a cryptographic signature using a trusted, independently distributed public key. At minimum, verify a version-specific SHA-256 checksum obtained through a separate authenticated channel.
- Abort installation if signature, checksum, expected origin, or version verification fails.
- Allow the user to inspect the downloaded artifact and require explicit approval before execution.
- Avoid requesting administrator or root privileges unless a documented installation step strictly requires them. Prefer installation into a user-owned directory.
- Apply equivalent verification and approval controls to both the Bash and PowerShell installation paths.
- Keep installation outside normal Skill execution. If
oois unavailable, return a clear error and provide a safe installation guide rather than automatically executing setup commands.
