Back to skill

Security audit

Netlify

Security checks for vulnerabilities and agentic risk

Overview

This Netlify skill is coherent and disclosed, but users should be careful with its one-time CLI install command and confirm any Netlify changes before running them.

Install the oo CLI only from a source you trust, preferably with a verified installer if OOMOL provides one. Treat the connected Netlify account as powerful: allow read actions as needed, but review the exact site, deploy, submission, and payload before approving any write or destructive action.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

The skill instructs users to install the CLI via a remote script piped directly into a shell (curl ... | bash), which executes unreviewed network-fetched code immediately. If the hosting endpoint, transport, or upstream release pipeline is compromised, this becomes a straightforward remote code execution path on the user's machine.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The description says to use this skill for ANY Netlify request instead of calling the API directly, which creates an overly broad auto-invocation trigger. That can cause the agent to route unrelated or sensitive Netlify-adjacent tasks through a high-privilege connector without sufficient task scoping or user intent validation, increasing the chance of unintended read/write/destructive operations.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.