Malicious File Detection: Wazuh to VirusTotal + Slack Alerts

Automates Wazuh alert ingestion for suspicious files, validates hashes via VirusTotal, generates summaries, and routes notifications/tickets via Slack/Gmail based on threat level.

n8n
Malicious File Detection: Wazuh to VirusTotal + Slack Alerts

This n8n workflow streamlines SOC operations by ingesting Wazuh alerts on potential malicious files via a webhook, extracting key IOCs like SHA256/MD5 hashes and filenames using Function nodes, and querying VirusTotal's API for real-time reputation checks.

It then generates a structured, human-readable threat summary and employs If/Switch logic to route actions: always sending a Gmail email with details, while escalating high-threat files by creating incident tickets and firing urgent Slack alerts to the team. This eliminates manual triage delays, providing instant context and reducing false positives through enriched intelligence.

Ideal for security teams handling file-based threats, it saves hours per incident by automating validation, reporting, and escalation. Benefits include faster response times, centralized alerting, and scalable threat hunting without custom coding, leveraging proven integrations for reliable performance in production environments.

Tech stack: Wazuh for detection, VirusTotal for intel, n8n orchestration, Slack/Gmail for comms, and incident tools for ticketing. Perfect for IT/security pros seeking zero-touch file threat automation.

$24.99
Last updated October 17, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Communication workflows

More from Bruno Lindberg

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.