Security audit
Security checks for vulnerabilities and agentic risk
The Gumloop actions have sensible safeguards, but setup can execute unverified code and introduce broader changes to your agent’s skills without clear approval.
Review and approve the CLI installation separately, preferably using a pinned, verified release. Trusting this integration also means trusting OOMOL with your connected Gumloop account and task data. Before using the CLI, review its automatic skill installation; current documentation provides OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. Keep the skill’s confirmation requirements for starting or stopping flows. Remote installers and hosted behavior were not verified; no malicious behavior was established in the supplied artifact.
The supplied command installs software from an unrelated service and shows no Gumloop functionality or established supporting role for Gumloop operations. The remote script's contents are not supplied, so its further effects cannot be determined.
The command streams a mutable remote installer directly into Bash without pinning or verifying its contents. HTTPS protects transport but does not prevent a compromised distribution endpoint from supplying code that steals accessible credentials or modifies local files; the documented OOMOL dependency explains the destination but does not eliminate this supply-chain risk.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
When the CLI is missing, the skill instructs installation through remotely fetched shell or PowerShell code without explicit approval or integrity verification. Although this is conditional setup rather than hidden execution, it expands a Gumloop task into host-system modification and could execute malicious code with the invoking user's privileges if the installation source is compromised.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources