Security audit
Security checks for vulnerabilities and agentic risk
The AbuseIPDB lookups fit the stated purpose, but setup can execute unchecked downloaded software and make broader agent changes without clear user approval.
Review and approve CLI installation separately, preferably using a verified release. OOMOL will mediate your queries and hold the connected service credentials. Its current CLI documents automatic skill synchronization; inspect or disable that behavior before use using its documented OO_SKILLS_SYNC_DISABLED setting. All bundled content was inspected, but the remote installers and hosted connector implementation were not verified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)
The supplied command accesses an unrelated installation endpoint and executes its response. No AbuseIPDB access or data-reading functionality is shown, nor is there evidence that this installation is a supporting dependency for such functionality. The remote script's further effects cannot be determined from the supplied code.
The supplied chunk contains only a login command, not AbuseIPDB search or read functionality. Authentication could be a supporting implementation detail if tied to AbuseIPDB, but the supplied code establishes no such connection and instead exposes a materially different immediate purpose.
The command pipes a mutable network response directly into Bash without pinning or independently verifying the downloaded artifact. HTTPS protects transport but does not prevent a compromised distribution endpoint from supplying malicious code capable of accessing local files and credentials; the PowerShell example has the same underlying 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 dependency triggers instructions to execute a downloaded installer without explicitly obtaining approval for arbitrary code execution and local system changes. Although dependency installation is relevant to the skill, a read-oriented request does not itself authorize installation, and a compromised installer could execute with the invoking account's permissions.
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