Security audit
Security checks for vulnerabilities and agentic risk
This Pinata helper needs review because its approval rules overlook pinning content and its setup directly executes remote installation code.
Require confirmation of the CID, destination account, and storage effect before pinning. Install the CLI through a separately reviewed, verified process and check its documented changes to other agent skills. Connecting Pinata entrusts OOMOL with account access. The remote installer and hosted connector behavior were not verified.
The code's sole visible action is executing an installer from a non-Pinata domain. Nothing in the supplied chunk establishes that this installation supports Pinata functionality, so it represents a materially different action rather than a demonstrated supporting implementation detail. The downloaded script's contents and subsequent effects cannot be determined from this chunk.
Piping a remote installer directly into bash executes mutable network-delivered code with the agent process's privileges, without version pinning, integrity verification, or a separate approval step; the PowerShell alternative has the same issue. A compromised distribution endpoint could therefore execute arbitrary code or steal accessible credentials, 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 pin_by_cid action requests persistent pinning, but it has no write tag and therefore falls under the explicit instruction that untagged actions are safe reads. This bypasses the skill's user-confirmation gate and can cause unintended account changes, storage consumption, or quota usage.
This is the same confirmation-bypass defect identified by SDI-4, not an additional independent vulnerability. Treating the state-changing pin_by_cid action as a safe read allows the agent to initiate pinning without the approval required for other writes.
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