Back to skill

Security audit

Email Outreach Automation

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent self-hosted outreach automation skill, but its public webhooks and automated email workflows need review before use because they can modify prospect records and send notifications without enough safeguards.

Review before installing. Use only with lawful, consent-aware prospect lists; configure a strong OUTREACH_SECRET and fail closed if it is missing; authenticate or signature-verify reply webhooks; add rate limits and request-size limits; use suppression and opt-out handling; restrict Google Sheets and SMTP credentials to the minimum needed; validate admin report recipients; and avoid rendering raw reply content as HTML.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • 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
Findings (3)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
workflows/03-reply-tracker.json:4
Finding

Unauthenticated Reply Webhook Allows Unauthorized CRM Modification and Notification Flooding

Content
View full analysis
Reply Received

From: {{ $json.email }}

Subject: {{ $json.subject }}

Message:

{{ $json.message }}

Time: {{ $json.replied_at }}

" }, "name": "Notify Team", "type": "n8n-nodes-base.emailSend" } ``` ### Technical Analysis The `outreach/reply` webhook ...[truncated 2022 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
workflows/03-reply-tracker.json:137
Finding

Attacker-Controlled Reply Content Is Embedded in Administrator HTML Email Without Escaping

Content
View full analysis
Reply Received

From: {{ $json.email }}

Subject: {{ $json.subject }}

Message:

{{ $json.message }}

Time: {{ $json.replied_at }}

", "options": {} }, "id": "n5", "name": "Notify Team", "type": "n8n-nodes-base.emailSend", "typeVersion": 2.1 } ``` ### Technical Analysis The webhook reads `email`, `subject`, and `message` directly from an untrusted request. These values are interpolated into an HTML-formatted administrator email without HTML encoding or sanitization. An attacker can inject arbitrary HTML elements, including deceptive links, externally hosted images, and tracking pixels. Modern email clients commonly block scripts, so arbitrary JavaScript execution is not established by the audited code. However, email-client sanitization does not reliably prevent phishing content, misleading formatting, unsafe links, or privacy leakage through remote resources. This issue is amplified by the absence of authentication on the reply webhook, although HTML encoding remains necessary even aft ...[truncated 1385 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
workflows/01-prospect-import.json:23
Finding

Predictable Fallback Secret Causes Prospect Import Authentication to Fail Open on Misconfiguration

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (9)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill automates collection, storage, and processing of personal contact data for unsolicited outreach, but it does not warn users about privacy, consent, anti-spam, or jurisdiction-specific compliance requirements. In context, this is dangerous because the workflow is explicitly designed for bulk cold-email sequencing and reply tracking, which can lead to unlawful processing of personal data, policy violations, or misuse at scale if deployed without safeguards.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

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

4. Import Prospects

bash
curl -X POST https://your-n8n.com/webhook/outreach/import \
  -H "Content-Type: application/json" \
  -d '{
    "_secret": "your-outreach-secret",

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

This JSON workflow performs a data write operation by appending or updating prospect records in Google Sheets, including emails and other contact details. In this file there is no confirmation step, user-facing log/notice, or descriptive comment warning that submitted webhook data will be stored externally.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

This JSON workflow sends emails via SMTP using prospect data from a Google Sheet, but the file contains no natural-language warning, confirmation step, or user-facing disclosure about transmitting recipient data or performing automated outreach. Because this is a manifest/config file with embedded operational definitions rather than a markdown description, there is no visible in-file notice to alert operators about the behavior.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The webhook accepts reply data and forwards the sender email, subject, and full message body to an admin email address without any authentication, consent notice, or minimization. If the webhook is exposed or abused, attacker-supplied content and potentially sensitive correspondence can be relayed externally through SMTP, creating a privacy leak and data-handling risk.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The workflow automatically emails aggregated outreach metrics derived from the Prospects sheet, which may contain sensitive business or prospect-related data, to a recipient without any validation, minimization, or approval step. If the SMTP recipient is misconfigured or the mailbox is insecure, internal campaign activity and prospect information can be exposed to unauthorized parties on a recurring basis.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

The manifest describes reply tracking, bounce handling, campaign analytics, Google Sheets CRM, and SMTP integration for outreach automation. In this workflow, SMTP is used to forward full reply contents to an admin notification address, which is an additional alerting/forwarding capability beyond simply tracking replies in the CRM.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

This JSON workflow runs from a generic daily schedule trigger, but the manifest-style description in the file does not define any scope constraints, exclusions, or operator expectations around when the workflow should or should not run. For manifest/config files, vague activation conditions can lead to unintended execution because there is no documented boundary beyond a 24-hour interval.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
86% confidence
Finding

The recipient address is taken from an environment variable, which creates a covert configuration path for where reports are sent and can redirect data externally if the environment is altered or misconfigured. In this workflow, that risk is amplified because the value controls automatic delivery of prospect-derived reporting data without any in-workflow verification or disclosure.

Content

No source excerpt is available for this finding.