Back to skill

Security audit

n8n工作流自动化

Security checks for vulnerabilities and agentic risk

Overview

This is a small text-only skill for generating n8n workflow JSON, with no executable code or hidden persistence found.

Before installing, note that the skill appears safe as a text generator, but review any generated n8n workflow before importing or running it because the generated workflow could still call APIs, use credentials, or change external systems depending on your prompt.

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
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
83% confidence
Finding

The visible title, description, usage, trigger text, and safety statement are presented only in Chinese, with no indication that the user can choose another language. This can violate a language/locale policy when a skill imposes a specific language without explicit opt-in or documented regional justification.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger condition is defined as any message containing the skill name or related instructions, which is overly broad and ambiguous. This can cause unintended invocation, prompt-routing mistakes, or make it easier for an attacker to activate the skill in contexts where workflow generation was not explicitly requested, increasing the chance of unsafe or unauthorized automation output.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.