Security audit
Security checks for vulnerabilities and agentic risk
The Tremendous workflow requires approval for account changes, but its setup instructions can execute downloaded software without asking first.
Review before installing because the missing-CLI fallback executes an unverified remote installer automatically. Install a reviewed CLI release yourself and prevent automatic setup. Connecting Tremendous gives OOMOL access to the account; retain the required confirmation for reward orders and other writes. Installer contents and server-side implementation were unavailable for verification. No artifact-backed malicious behavior was found.
The supplied command performs remote script execution rather than any visible Tremendous operation. Although installing a dependency can be a supporting implementation detail, this chunk provides no evidence that the Oomol installer supports the declared Tremendous functionality. The downloaded script's contents and further effects cannot be determined from the supplied code.
Piping a mutable remote script directly into bash executes whatever the installation endpoint returns without integrity verification or a review opportunity. The domain is relevant to the connector and HTTPS protects transport, but neither prevents malicious code execution if the distribution endpoint or its publishing pipeline is compromised; the PowerShell alternative has the same weakness.
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
The fallback directs the agent to execute downloaded installation code without first explaining local changes or obtaining explicit installation approval. Although limited to a missing-CLI error, this expands an ordinary Tremendous request into local code execution, and a compromised installer could access files and credentials available to the executing user.
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