Security audit
Security checks for vulnerabilities and agentic risk
The Tongdaxin workflow is coherent, but setup runs an unverified remote installer and omits potentially broad changes to agent skills.
Review setup before installing. Prefer a verified CLI release installed under your control, and disable managed-skill synchronization with OO_SKILLS_SYNC_DISABLED=1 if unwanted. Connect only the intended account and retain destructive-action approvals. The remote installers and live connector implementation were not verified; no artifact-backed malicious intent was found.
The supplied code installs software from an external domain rather than performing Tongdaxin data operations. Nothing in the chunk establishes that this installation supports the declared purpose. The remote script's contents are not supplied, so its further behavior cannot be assessed.
Authentication could support a Tongdaxin integration, but the supplied chunk contains only a login command and establishes no connection to Tongdaxin or its declared data-management capabilities. As supplied, its sole behavior materially differs from the advertised purpose.
The curl-to-bash command immediately executes the current contents of a remote installer without pinning or integrity verification. Compromise of the installer host or delivery pipeline could therefore execute arbitrary code with the invoking user's privileges, potentially exposing local files and credentials; HTTPS alone does not protect against a compromised source.
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 directs the agent to execute downloaded shell or PowerShell code when the CLI is missing, without explicit user approval for running remote code or making local installation changes. This expands a financial-data task into local code execution; the conditional setup limits exposure but does not establish informed consent or installer integrity.
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