Security audit
Security checks for vulnerabilities and agentic risk
The Cardly workflow is coherent, but its fallback setup runs an unverified remote installer without clear user approval.
Review the dependency setup before installing. Arrange a separately approved, verified oo installation and check its bundled-skill installation and update behavior before allowing the agent to run it. Cardly requests pass through OOMOL, so connect only the intended account and review write payloads. The installer and hosted connector were not verified; no artifact-backed malicious behavior was found.
The supplied code performs remote script execution rather than Cardly data operations. Nothing in the chunk establishes the Oomol installer as a necessary Cardly implementation dependency. The downloaded script's contents are not supplied, so its precise effects cannot be determined.
The command executes a remotely fetched, unpinned script directly in a local shell without checking its integrity or reviewing it; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could yield arbitrary code execution with the agent's local privileges, although the missing-CLI condition limits when this path is reached.
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 fallback directs the agent to install software when the CLI is missing without first disclosing local system changes or obtaining installation approval. Although this is relevant dependency setup rather than hidden functionality, permission to perform a Cardly task does not necessarily authorize executing an installer on the user's machine.
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
- Cardly homepage: https://www.card.ly
- API documentation: https://api.card.ly/v2/docs