Security audit
Security checks for vulnerabilities and agentic risk
The Mocean workflow has sensible controls, but its setup executes unverified downloads and its CLI can silently install additional agent skills.
Review the CLI setup before installing. Prefer a verified, pinned CLI release and explicitly approve its installation. For compatible versions, set OO_SKILLS_SYNC_DISABLED=1 before running oo to prevent additional agent-skill installation. Confirm SMS recipients, message text, and charges, and consider that OOMOL processes the submitted data. The remote installers were unavailable for inspection; no malicious payload was established.
The supplied command performs no visible Mocean operation. Instead, it executes a third-party installer without any demonstrated role in supporting the declared Mocean functionality. The installer's contents and downstream effects are not provided, so those effects cannot be determined.
Piping an unpinned HTTPS response directly into bash executes the current remote content without prior inspection or independent integrity verification. Compromise of the installer distribution path could therefore lead to arbitrary code execution, local data theft, or persistent modifications, although the command is only proposed when the CLI is missing.
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 missing-CLI fallback directs installation through immediate execution of downloaded shell or PowerShell content without an explicit installation approval step or integrity verification. Although this is conditional setup rather than routine operation, it can execute attacker-controlled code with the agent's privileges if the distribution endpoint is compromised; the declared oo-only tool restriction may limit execution if enforced.
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