Back to skill

Security audit

Get Biji

Security checks for vulnerabilities and agentic risk

Overview

The Get Biji workflow has clear safeguards, but setup can execute unverified remote code and introduce broader agent changes without clear approval.

Review and install the CLI separately before using this skill. Check its agent-skill synchronization settings and approve any additional host changes. OOMOL mediates access to your Get Biji account. The remote installers were unavailable for inspection, so their exact effects remain uncertain.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
92% confidence
Finding

The visible behavior is remote software installation rather than Get Biji data management. Installing a dependency could be a supporting implementation detail, but the supplied code does not establish that this installer supports the declared purpose. The downloaded script's contents and any further effects are not available for assessment.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping an unpinned remote script directly into bash executes whatever the installer endpoint serves with the invoking user's privileges, without an integrity check or review step. HTTPS protects transport but does not prevent a compromised distribution endpoint from serving malicious code; the legitimate CLI dependency explains the download but does not eliminate this supply-chain risk.

Content

Scanner excerpt · SKILL.md (reported line 77)May include surrounding context.

Fallback setup executes downloaded installer scripts without warning the user about remote code execution or system changes.

Medium
Category
Output Handling
Confidence
93% confidence
Finding

The fallback directs the agent to execute a downloaded installer without first explaining its local code-execution and system-modification effects or obtaining installation approval. The missing-CLI condition limits exposure, but requesting Get Biji operations does not necessarily authorize installing software on the host.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

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.

Content

Scanner excerpt · SKILL.md (reported line 98)May include surrounding context.

md
- **`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