Back to skill

Security audit

Fluxguard

Security checks for vulnerabilities and agentic risk

Overview

Fluxguard changes require approval, but fallback setup executes unverified remote code and can introduce persistent changes to agent skills without explaining them.

Review and approve the CLI installation separately before allowing fallback setup. Understand that Fluxguard requests pass through OOMOL. Review the CLI's automatic skill synchronization and disable it if unwanted. The remote installers were unavailable for inspection, so their exact local changes 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
98% confidence
Finding

The supplied command performs remote software installation, not Fluxguard data operations. Nothing in the provided chunk establishes that the Oomol installer supports Fluxguard, so it cannot be treated as a demonstrated supporting implementation detail. The downloaded script's contents and 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 the HTTPS response directly into bash executes whatever the installation endpoint returns without a review or artifact-verification step. HTTPS protects transport but does not protect against a compromised publisher or installation service, making this a conditional supply-chain execution risk rather than evidence of malicious intent; it overlaps with SQP-2.

Content

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

Fallback setup instructs execution of remotely downloaded installation scripts without a system-integrity warning.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The fallback setup directs the agent to execute downloaded shell or PowerShell code without inspecting it, verifying a pinned artifact, or obtaining explicit approval for local installation. If the installation endpoint or delivery pipeline is compromised, that code could access files and credentials or modify the system with the executing user's privileges; the missing-CLI condition limits exposure but does not establish trust.

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 87)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