Security audit
Security checks for vulnerabilities and agentic risk
The Globalping workflow is coherent, but its setup runs unverified remote installers without clear approval and under-discloses broader changes to agent skills.
Review and approve CLI installation separately, preferably using a verified, pinned release. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization; consider setting it before invoking the CLI. Approve measurement targets and payloads, and understand that OOMOL mediates requests and billing. The remote installers' complete effects remain unverified.
The supplied command installs software from cli.oomol.com and contains no Globalping interaction. Nothing in the supplied material establishes this installer as a supporting dependency for the declared purpose. The remote script's contents are unavailable, so its specific effects cannot be determined.
The command pipes a mutable network response directly into a shell without verifying a pinned artifact or its authenticity independently of the download channel. Compromise of the installer delivery infrastructure could therefore execute attacker-controlled code with the agent's local permissions; the legitimate provider domain and missing-CLI prerequisite reduce exposure but do not eliminate this 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
A missing CLI triggers instructions to install software without first obtaining approval for executing remote code and modifying the local environment. The conditional fallback reduces exposure, but authorization to perform Globalping operations does not necessarily authorize installing software.
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