T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:59- Finding
Unverified Remote Installation Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 59–63
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 download mutable content from
cli.oomol.comand immediately execute the response with Bash or PowerShell. They do not pin a release version, verify a cryptographic signature or checksum, save the installer for inspection, or use a constrained execution environment.Although the download domain is consistent with the declared OOMOL provider, the retrieved scripts are not included in the audited project. Their contents and future changes therefore cannot be reviewed as part of this Skill. Compromise of the hosting infrastructure, publishing account, DNS path, or TLS termination environment could cause attacker-controlled commands to be executed.
Installing the CLI is only a conditional setup operation and is not required for ordinary DingTalk connector actions when the CLI is already present. Automatically executing an unverified installer exceeds the minimum privileges necessary to send DingTalk messages.
Attack Path
- The
ooCLI is unavailable, causing the first-time setup instructions to be used. - The user or agent runs one of the documented installation commands.
- The command retrieves the current response from the external OOMOL installation endpoint.
- No version, checksum, or signature is validated.
- Bash or PowerShell immediately interprets the downloaded response.
- If the remote distribution path has been compromised, attacker-supplied commands execute with the permissions of the invoking user.
Impact Assessment
A malicious remote installer could execute arbitrary commands with ...[truncated 530 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove direct pipe-to-shell and
Invoke-Expressioninstallation commands. - Direct users to a pinned, versioned release artifact from an official distribution channel.
- Download the installer or binary to disk without executing it automatically.
- Verify the artifact against a publisher-signed manifest or a pinned SHA-256 checksum distributed through an independent trusted channel.
- Provide commands that stop immediately when integrity or signature verification fails.
- Allow users to inspect the downloaded artifact before execution.
- Require explicit user approval before installing software or making system changes.
- Prefer a trusted operating-system package manager or signed package format where available.
- Run installation with ordinary user permissions unless a specific, documented operation requires elevation.
- Remove direct pipe-to-shell and
