T1567.004 Microsoft Sentinel · KQL

Detect Exfiltration Over Webhook in Microsoft Sentinel

Adversaries may exfiltrate data to a webhook endpoint rather than over their primary command and control channel. Webhooks are simple HTTP/S push mechanisms supported by collaboration platforms such as Discord, Slack, Microsoft Teams, and generic services like webhook.site. Adversaries exploit these endpoints by either linking an adversary-controlled webhook to a victim-owned SaaS service for automated repeated exfiltration of emails or chat messages, or by manually posting staged data directly to a webhook URL via scripting tools. Because webhook traffic is HTTPS and destined for widely-trusted SaaS domains, it blends with normal enterprise traffic and often bypasses data loss prevention controls. Observed real-world usage includes Discord webhooks for credential and token exfiltration from malicious npm packages, Slack webhooks used by insider threats, and Microsoft Teams webhooks abused via SQL Server xp_cmdshell lateral movement chains.

MITRE ATT&CK

Tactic
Exfiltration
Technique
T1567 Exfiltration Over Web Service
Sub-technique
T1567.004 Exfiltration Over Webhook
Canonical reference
https://attack.mitre.org/techniques/T1567/004/

KQL Detection Query

Microsoft Sentinel (KQL)
kusto
let WebhookDomains = dynamic([
  "discord.com", "discordapp.com",
  "hooks.slack.com", "slack.com",
  "webhook.site", "webhooks.site",
  "outlook.office.com", "outlook.office365.com",
  "pipedream.net", "requestbin.com", "requestcatcher.com",
  "hookbin.com", "beeceptor.com", "smee.io",
  "ntfy.sh", "pushover.net"
]);
let SuspiciousInitiators = dynamic([
  "powershell.exe", "pwsh.exe", "cmd.exe",
  "python.exe", "python3", "node.exe",
  "curl.exe", "wget.exe", "wscript.exe", "cscript.exe",
  "mshta.exe", "rundll32.exe", "regsvr32.exe",
  "bitsadmin.exe", "certutil.exe"
]);
// Signal 1: Network connections to webhook domains from suspicious processes
let WebhookNetworkHits = DeviceNetworkEvents
| where Timestamp > ago(24h)
| where RemoteUrl has_any (WebhookDomains)
  or RemoteUrl matches regex @"/api/webhooks/\d+/"
  or RemoteUrl has "/services/T"
| where InitiatingProcessFileName in~ (SuspiciousInitiators)
| extend Signal = "WebhookNetConn"
| extend WebhookDomain = RemoteUrl
| project Timestamp, DeviceName, AccountName, Signal,
    InitiatingProcessFileName, InitiatingProcessCommandLine,
    RemoteUrl, RemoteIP, RemotePort, BytesSent, BytesReceived,
    WebhookDomain;
// Signal 2: Large outbound transfers to webhook domains (any process, high volume)
let WebhookLargeTransfer = DeviceNetworkEvents
| where Timestamp > ago(24h)
| where RemoteUrl has_any (WebhookDomains)
  or RemoteUrl matches regex @"/api/webhooks/\d+/"
  or RemoteUrl has "/services/T"
| where BytesSent > 1048576  // > 1MB sent
| extend Signal = "WebhookLargeTransfer"
| extend WebhookDomain = RemoteUrl
| project Timestamp, DeviceName, AccountName, Signal,
    InitiatingProcessFileName, InitiatingProcessCommandLine,
    RemoteUrl, RemoteIP, RemotePort, BytesSent, BytesReceived,
    WebhookDomain;
// Signal 3: Process command lines containing webhook URL patterns
let WebhookCmdLine = DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine matches regex @"(discord\.com/api/webhooks|hooks\.slack\.com/services|webhook\.site|outlook\.office(\.com|365\.com)/webhook|pipedream\.net|requestbin\.com|hookbin\.com|beeceptor\.com|ntfy\.sh)"
| extend Signal = "WebhookCmdLine"
| extend WebhookDomain = extract(@"https?://([^/]+)", 1, ProcessCommandLine)
| project Timestamp, DeviceName, AccountName, Signal,
    FileName as InitiatingProcessFileName, ProcessCommandLine as InitiatingProcessCommandLine,
    RemoteUrl="(from cmdline)", RemoteIP="", RemotePort=0, BytesSent=0, BytesReceived=0,
    WebhookDomain;
union WebhookNetworkHits, WebhookLargeTransfer, WebhookCmdLine
| summarize
    Signals=make_set(Signal),
    SignalCount=dcount(Signal),
    TotalBytesSent=sum(BytesSent),
    WebhookTargets=make_set(WebhookDomain),
    CommandLines=make_set(InitiatingProcessCommandLine),
    FirstSeen=min(Timestamp),
    LastSeen=max(Timestamp),
    EventCount=count()
    by DeviceName, AccountName, InitiatingProcessFileName
| extend MultiSignal = SignalCount > 1
| sort by SignalCount desc, TotalBytesSent desc
high severity medium confidence

Detects data exfiltration via webhook endpoints using three correlated signals: (1) outbound network connections from suspicious scripting/LOLBin processes to known webhook service domains including Discord, Slack, Teams, and generic webhook testing services; (2) large outbound data transfers exceeding 1MB to webhook domains from any process; (3) process command lines containing webhook URL patterns indicating direct invocation of curl, PowerShell Invoke-WebRequest, or Python requests against webhook endpoints. Results are aggregated per device/account/process with signal counts and total bytes sent to prioritize high-fidelity events.

Data Sources

Network Traffic: Network Connection CreationProcess: Process CreationCommand: Command ExecutionMicrosoft Defender for Endpoint

Required Tables

DeviceNetworkEventsDeviceProcessEvents

False Positives & Tuning

  • Legitimate DevOps and CI/CD pipelines posting build status notifications to Slack or Teams webhooks via scripts or pipeline agents
  • IT monitoring and alerting tools (PagerDuty integrations, Grafana alerting, custom scripts) sending operational alerts to collaboration webhooks
  • Developer workstations testing webhook integrations during application development, especially when using webhook.site or requestbin as debug targets
  • Authorized security tools performing phishing simulations or red team exercises that post results to team notification webhooks
  • Business automation scripts (Zapier alternatives, custom workflow tools) that legitimately transfer structured data to webhooks
Download portable Sigma rule (.yml)

Other platforms for T1567.004


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Exfiltrate Data via Discord Webhook using PowerShell

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe, CommandLine containing 'Invoke-RestMethod' and 'webhook.site'. Sysmon Event ID 3: Network Connection from powershell.exe to webhook.site on port 443. DeviceNetworkEvents: RemoteUrl containing webhook.site, InitiatingProcessFileName=powershell.exe, BytesSent > 0.

  2. Test 2Exfiltrate File Contents via curl to Webhook Endpoint

    Expected signal: Sysmon Event ID 1: Process Create for cmd.exe (echo/type) and curl.exe with CommandLine containing 'webhook.site' and '-X POST'. Sysmon Event ID 11: File Create for the staging file in %TEMP%. Sysmon Event ID 3: Network Connection from curl.exe to webhook.site on port 443. DeviceNetworkEvents: InitiatingProcessFileName=curl.exe, RemoteUrl containing webhook.site.

  3. Test 3Python Requests Library Webhook Exfiltration

    Expected signal: Sysmon Event ID 1: Process Create with Image=python.exe, CommandLine containing 'urllib.request', 'webhook.site', and 'POST'. Sysmon Event ID 3: Network Connection from python.exe to webhook.site on port 443. DeviceNetworkEvents: InitiatingProcessFileName=python.exe, RemoteUrl=webhook.site.

  4. Test 4Automated SaaS Webhook Exfiltration via Microsoft Teams Incoming Webhook

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe, CommandLine containing 'Invoke-WebRequest' and 'outlook.office.com/webhook'. Sysmon Event ID 3: Network Connection from powershell.exe to outlook.office.com on port 443. DeviceNetworkEvents: RemoteUrl containing /webhook/, InitiatingProcessFileName=powershell.exe.

Unlock Pro Content

Get the full detection package for T1567.004 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections