Security audit
Security checks for vulnerabilities and agentic risk
The DingTalk workflow has clear approval safeguards, but its setup can execute downloaded software without separate approval or integrity checks.
Review and approve CLI installation separately before allowing this fallback to run, using a reviewed, integrity-verified release. Check the CLI's automatic skill synchronization and disable it if unwanted. Connect only the intended DingTalk account and retain the explicit approval requirements for changes. The entire bundled artifact was inspected, but external installer and hosted-service behavior remain outside that inspection.
The supplied chunk performs remote software installation rather than DingTalk MCP operations. No visible code establishes that this installer is a supporting dependency for the declared functionality. The downloaded script's contents and subsequent effects are not available, so no specific downstream behavior or malicious intent can be established.
Piping the HTTPS response directly into bash executes mutable remote content without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could execute arbitrary commands with the invoking account's permissions, potentially exposing local files or credentials; the documented vendor relationship and missing-CLI condition do not eliminate that 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 missing-CLI fallback directs installation without requiring disclosure of local system changes or explicit approval to execute downloaded code. A DingTalk task does not necessarily authorize installing software; the conditional fallback limits exposure but can still lead to unexpected code execution under the agent's account.
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