Security audit
Security checks for vulnerabilities and agentic risk
The Splunk integration is clearly described, but its setup fallback directs execution of downloaded installers without verification or separate approval.
Review the setup path before installing. Prefer a verified CLI release and require approval before downloaded installation code runs. Confirm each event payload and consider whether its contents are appropriate to send through OOMOL. The complete bundled document was inspected, but remote installer behavior remains unverified.
The supplied command performs remote installer execution, not a Splunk HTTP Event Collector request. Although installation can be a supporting implementation detail, the provided chunk establishes no relationship between this installer and the declared Splunk functionality. The downloaded script's further behavior is not visible.
Authentication can be a supporting implementation detail, but the supplied chunk consists solely of a login command with no demonstrated connection to Splunk. Its observable purpose therefore differs materially from the declared Splunk data-access purpose. The command alone does not establish credential theft or other malicious behavior.
Piping the HTTPS response directly into bash executes mutable remote code without inspecting or verifying the downloaded artifact. Although the domain is consistent with the documented CLI provider and installation is conditional, compromise of the distribution endpoint or release pipeline could lead to local code execution and exposure of accessible files or credentials.
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 and PowerShell installers without an explicit installation approval gate or integrity verification. A missing CLI makes this path reachable during ordinary use, and a compromised installer could execute arbitrary code with the invoking user's privileges; the concern is execution of unverified code, not merely the missing warning.
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