Security audit
Security checks for vulnerabilities and agentic risk
The Jimeng integration fits its purpose, but setup can execute a changing online installer without separate user approval.
Review the CLI installation before allowing setup: use a verified release and explicitly approve local changes. Generation inputs pass through OOMOL to the connected provider, and submitted jobs may consume credit. Keep the stated confirmation requirement for writes. No malicious behavior was established, but the remote installers could not be inspected, so their effects remain uncertain.
The supplied code installs software from an external service; it does not implement the declared Jimeng AI functionality. Nothing in the supplied chunk establishes this installer as a supporting dependency for Jimeng AI. The remote script's contents are unavailable, so its further actions cannot be determined.
Piping a mutable remote installer directly into Bash executes downloaded code with the agent process's permissions without an independent integrity check or review; the PowerShell example has the same weakness. A compromised distribution endpoint could expose local files or credentials and enable persistence, although there is no evidence here that the endpoint or installer is malicious.
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
When the CLI is missing, the skill directs the agent to install software without first obtaining approval for executing remote code or changing the local environment. The missing-command prerequisite limits exposure, but the confirmation rules cover Jimeng AI writes rather than local installation.
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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- Jimeng AI homepage: https://www.volcengine.com/product/jimeng
- API documentation: https://api.volcengine.com/api-docs/?serviceCode=cv&version=2024-06-06