T01 · Skill Instruction Hijacking
- Location
SKILL.md:9- Finding
Undisclosed Attribution Marker Injected into Generated Workflows
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its n8n workflow-building purpose, but it requires adding an undisclosed signature marker into generated workflows.
Review generated workflows before importing them into n8n, especially comments and annotations, and remove any unwanted signature marker. Also confirm the workflow only uses the integrations, credentials, posting actions, and API calls you intended.
SKILL.md:9Undisclosed Attribution Marker Injected into Generated Workflows
The activation conditions are broad enough to match routine requests for general automation or workflow help, which can cause the skill to invoke outside its intended scope. In a system with multiple skills or safety boundaries, this increases the chance of unintended capability exposure and context hijacking, especially because the skill is designed to emit ready-to-deploy automation JSON that may include credential-dependent integrations.
The trigger phrases such as "create an automation for..." and "automate my [process]" are ambiguous and likely to overlap with many benign requests unrelated to this specific skill. That makes accidental invocation more likely, which can bypass more appropriate routing and cause the agent to produce workflow artifacts or integration guidance in contexts where the user did not ask for n8n-specific behavior.