Security audit
Security checks for vulnerabilities and agentic risk
The Seq workflow has approval controls, but setup runs unverified downloaded code and leaves broader changes to agent skills unexplained.
Review before installing. Use a verified CLI release and explicitly approve installation rather than allowing the automatic downloaded-script fallback. Review or disable its documented skill synchronization before launch. Connect a narrowly scoped Seq account and consider whether its logs may pass through OOMOL. The bundled instructions were fully inspected, but the remote installers and hosted connector implementation remain unverified.
The supplied code performs remote script execution from an Oomol-hosted endpoint, rather than interacting with Datalust Seq. No connection between this installer and the declared Seq functionality is established, so it cannot be treated as a demonstrated supporting implementation detail. The downloaded script's contents are not supplied, so its further effects cannot be assessed.
Piping an HTTPS response directly into bash executes mutable remote code without a pinned version or independent integrity verification. Compromise of the installer delivery infrastructure could therefore lead to local code execution, credential theft, or file modification; the missing-CLI condition limits exposure but does not eliminate this supply-chain risk. This is the same installation path implicated by SQP-2, not a separate exploit chain.
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 setup directs the agent to execute remotely downloaded shell or PowerShell code without explicit installation approval or a stated verification step. A missing CLI is a legitimate prerequisite failure, but it does not authorize arbitrary installer code or its system changes; malicious installer content would run with the invoking 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