Security audit
Security checks for vulnerabilities and agentic risk
The WhatsApp functions are clearly explained, but automatic setup can execute unverified code and introduce broader agent changes without clear user control.
Review the setup before installing. Prefer a separately verified, fixed CLI release and explicitly approve local installation. Check whether its automatic skill synchronization will change other agents, and disable that behavior if unwanted. OOMOL mediates WhatsApp access, so consider the privacy of messages processed through it. Installer contents and the external runtime could not be verified.
The supplied command executes an Oomol-hosted installer rather than performing WhatsApp Chat API operations. Nothing in the chunk establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents are not supplied, so its further effects cannot be determined.
The supplied chunk only invokes a CLI login command; it contains no WhatsApp API operations or evidence that oo authenticates to chat-api.com. Authentication could be a supporting implementation detail if that relationship were established, but the supplied code does not establish it.
The command pipes a mutable network response directly into Bash without pinning or verifying the script. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from supplying malicious code; the legitimate CLI dependency explains the download but does not eliminate that 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
The fallback directs execution of downloaded shell or PowerShell code without a separate approval step or artifact verification. Although setup occurs only when the CLI is missing, a compromised installer source could execute arbitrary code with the agent's local privileges, and the write-confirmation rules cover WhatsApp changes rather than local installation.
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