Security audit

Netlify

Security checks for vulnerabilities and agentic risk

Overview

This Netlify deployment skill is mostly coherent and purpose-aligned, but one bundled helper can write unsafe Netlify configuration from unvalidated input that could affect CI builds.

Review the helper scripts before use. Only pass normal Hugo version strings to scripts/hugo_netlify_toml.sh, inspect generated netlify.toml before committing or deploying it, and treat Netlify environment variables and NETLIFY_AUTH_TOKEN as secrets with least-privilege scope and rotation if exposed.

A.I.G

Vulnerability Patterns

Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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

Findings (1)

T09 · Insecure Skill Coding Practices

Warning

Location: scripts/hugo_netlify_toml.sh:7
Finding: Unvalidated Hugo Version Allows Netlify TOML Configuration Injection
Content: View full analysis
netlify.toml <
Remediation: View remediation
&2 exit 1 fi ``` 2. Keep the validated value quoted when generating the file: ```bash cat > netlify.toml <

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The skill instructs users to set environment variables in Netlify but does not warn that these values may include secrets and will be stored in the Netlify project configuration. In a deployment/CI context, users may place API keys, tokens, or credentials there without understanding the exposure and lifecycle implications, increasing the risk of accidental credential disclosure or misuse.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.