Security audit
Security checks for vulnerabilities and agentic risk
NetSuite changes require your confirmation, but setup can execute unverified software whose broader effects on agent skills are not disclosed.
Review and install a verified CLI release before using this skill. Check its automatic skill synchronization and disable it if unwanted; current documentation provides OO_SKILLS_SYNC_DISABLED. Use a NetSuite account limited to the records you need and review every write payload. The remote installers and hosted connector implementation were unavailable for inspection; no malicious behavior was established.
The supplied chunk performs remote software installation rather than NetSuite data operations. Installing a dependency could be a supporting implementation detail, but nothing in the provided description or code establishes that this installer supports NetSuite access. The downloaded script's contents are not supplied, so its further behavior cannot be assessed.
The curl-to-bash pipeline immediately executes mutable remote content without validating a pinned version, signature, or trusted digest. HTTPS protects transport but does not protect against compromise of the hosting infrastructure or publisher account; exploitation would allow code execution with the agent's local privileges. This is the same underlying installation risk identified by SQP-2, not an independent exploit.
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 setup workflow directs the agent to execute downloaded shell or PowerShell code without prior inspection, integrity verification, or explicit approval for local installation. Although this is conditional dependency setup rather than evidence of malicious intent, a compromised installer source could execute arbitrary code with the invoking user's privileges, potentially exposing local files and credentials.
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