Back to skill

Security audit

Terraform

Security checks for vulnerabilities and agentic risk

Overview

The Terraform read workflow fits its purpose, but fallback setup executes unverified remote installers without first requesting your approval.

Before use, install a reviewed, pinned CLI release yourself and review any changes it makes to installed agent skills. Use a Terraform API key limited to the reads you need, and understand that OOMOL brokers access to your account. The bundled text shows no credential theft or destructive Terraform operation, but it cannot establish the safety of mutable remote installers or hosted services.

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 (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied command performs remote installer execution rather than Terraform data retrieval. Nothing in the chunk establishes this installer as a supporting dependency for the declared Terraform functionality. The downloaded script's contents are not supplied, so its further effects cannot be determined.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
88% confidence
Finding

Authentication can be a supporting implementation detail, but the supplied chunk contains only a login command and establishes no connection to Terraform access. As supplied, its primary behavior differs materially from the declared purpose. The command alone does not establish credential theft or data exfiltration.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The command pipes mutable, remotely fetched content directly into Bash without version pinning or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint or release pipeline could execute attacker-controlled code with the agent's OS permissions, potentially exposing local files and credentials; HTTPS and the legitimate dependency context do not eliminate this supply-chain risk.

Content

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

The setup workflow instructs the agent to execute a downloaded installer without warning the user about remote code execution or system changes.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

A missing CLI triggers instructions to install software by executing a remote script without first obtaining approval for local system changes. Although conditional and operationally relevant, this expands a Terraform read request into code execution and installation; the declared Bash tool restriction may limit execution but is not a substitute for a safe setup policy.

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