Security audit
Security checks for vulnerabilities and agentic risk
The Lusha workflow is coherent, but automatic remote installation and undisclosed changes to agent skills warrant review.
Review and approve CLI installation separately rather than allowing the missing-command fallback to execute downloaded scripts automatically. The installer payload remains unverified. Also review the CLI's automatic agent-skill changes; its command reference documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. [Command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) Using this integration entrusts OOMOL with your connected Lusha account and submitted queries.
The supplied command runs an Oomol installer rather than searching or reading Lusha data. Although dependency installation can be a supporting implementation detail, the supplied chunk establishes no relationship between this installer and the declared Lusha functionality. The downloaded script's contents and further effects are not available for inspection.
The command streams a remotely fetched, unpinned script directly into Bash without independent integrity verification or review; the PowerShell alternative uses the same execution pattern. A compromised distribution endpoint could execute arbitrary code with the invoking user's access, including access to local files and credentials. HTTPS and the legitimate CLI dependency reduce suspicion of malicious intent but do not eliminate 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
A missing CLI triggers instructions to install software without first obtaining approval or explaining the resulting system changes. Although conditional setup is appropriate to the workflow, authorization to retrieve Lusha data does not necessarily authorize installing executable software on the host.
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