Security audit
Security checks for vulnerabilities and agentic risk
The Kustomer workflow is coherent, but setup can execute a remote installer without separate approval or clear limits on local changes.
Review and approve dependency installation separately. Use a verified CLI release and review or disable its automatic skill synchronization. OOMOL will mediate access to customer data; grant only needed permissions and retain confirmation for changes. The remote installer and hosted connector implementation were unavailable for inspection.
The supplied command performs remote script execution for an Oomol installation. The chunk contains no Kustomer operations or evidence that this installer supports the declared Kustomer functionality. The downloaded script's additional behavior cannot be determined from the supplied code.
Piping the HTTPS installer directly into bash executes whatever the endpoint returns without an independent integrity check or review; the PowerShell example has the same weakness. Compromise of the distribution endpoint could therefore enable arbitrary code execution, local data theft, or tampering under the invoking user's privileges; the legitimate vendor relationship and missing-CLI condition reduce exposure but do not remove 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
The fallback directs installation through remotely downloaded shell or PowerShell code without requiring explicit approval for local system changes. Although installation is conditional on a missing CLI and serves a legitimate dependency, a routine Kustomer request can thereby expand into execution of unreviewed code with the agent process's privileges.
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