Security audit
Security checks for vulnerabilities and agentic risk
The LeadIQ features fit their purpose, but setup can execute unverified downloaded code and make broader agent changes without clear user control.
Review and approve the CLI installation separately, including changes to other agents' skills. Prefer a verified release and consider the documented OO_SKILLS_SYNC_DISABLED control. Using this integration entrusts LeadIQ access and query data to OOMOL. The downloaded installers and server-side connector were not verified; no malicious behavior was established.
The supplied code contains no LeadIQ search or read operations and does not establish that the installer supports LeadIQ. Executing a remote installation script is an undeclared capability, not a demonstrated supporting implementation detail of the stated purpose. The downloaded script's further behavior cannot be determined from this chunk.
The command pipes a mutable remote script directly into Bash without pinning or verifying its contents; the PowerShell alternative has the same weakness. If the distribution endpoint or release pipeline is compromised, attacker-controlled code could run with the agent process's local permissions and access files or credentials. The documented vendor domain and missing-CLI condition make this plausible legitimate setup, but do not eliminate the 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 instructs the agent to install software by executing a remote script without requiring explicit approval or explaining the resulting local system changes. Although limited to missing-CLI errors, this expands a LeadIQ data-access task into local code execution without a clear consent boundary; this overlaps with the SC2 finding.
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