Direct Network Flood
Adversaries may attempt to cause a denial of service (DoS) by directly sending a high-volume of network traffic to a target. Direct Network Floods use one or more systems to send high-volume network packets toward the targeted service or network. Any network protocol may be used — stateless protocols such as UDP and ICMP are common due to their low overhead, but TCP SYN floods are also prevalent. Botnets are frequently leveraged to amplify attack volume, with compromised endpoints acting as unwitting flood sources. Organizations may detect this technique either as a victim observing inbound traffic spikes, or by identifying compromised endpoints in their environment participating in an outbound DDoS campaign as botnet nodes.
// T1498.001 — Direct Network Flood
// Detects known DDoS/flood tool execution on endpoints (botnet participants, insider threat, red team)
let FloodToolNames = dynamic([
"hping3", "hping", "nping", "trafgen", "t50",
"loic", "hoic", "mhddos", "ufonet", "goldeneye", "xerxes",
"udpflood", "synflood", "icmpflood", "pyflood", "rudy",
"packetsender", "ostinato", "netcat"
]);
let FloodArgPatterns = dynamic([
"--flood", "-i u0", "--rand-dest", "--rand-source",
"--syn --flood", "--icmp --flood", "--udp --flood",
"-c 999999", "--count 9999999", "--faster", "--turbo",
"--rate 100000"
]);
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName has_any (FloodToolNames)
or ProcessCommandLine has_any (FloodToolNames)
or ProcessCommandLine has_any (FloodArgPatterns)
| extend IsKnownFloodTool = FileName has_any (FloodToolNames)
or ProcessCommandLine has_any (FloodToolNames)
| extend HasFloodArgs = ProcessCommandLine has_any (FloodArgPatterns)
| extend SuspicionLevel = case(
IsKnownFloodTool and HasFloodArgs, "Critical",
IsKnownFloodTool, "High",
HasFloodArgs, "Medium",
"Low")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine,
InitiatingProcessFileName, InitiatingProcessCommandLine,
IsKnownFloodTool, HasFloodArgs, SuspicionLevel
| sort by Timestamp desc Data Sources
Required Tables
False Positives
- Load testing tools (Apache Bench, wrk, hey, vegeta, k6) run legitimately by QA engineers or DevOps teams against internal staging environments or authorized external endpoints
- Network performance benchmarking tools (iperf, iperf3, netperf, iperf) used by infrastructure teams to validate bandwidth capacity on new circuits or after changes
- Security scanners using aggressive timing profiles (nmap -T5, masscan) operated by internal vulnerability management or red team programs with authorized change tickets
- Authorized DDoS simulation exercises where security vendors run flood tools against hardened DMZ systems to validate WAF or DDoS protection efficacy
- Academic, research, or sandbox environments where flood tools are used for network research, coursework, or tool development without malicious intent
References (8)
- https://attack.mitre.org/techniques/T1498/001/
- https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/netflow/configuration/15-mt/nf-15-mt-book/nf-detct-analy-thrts.pdf
- https://www.justice.gov/opa/pr/seven-iranians-working-islamic-revolutionary-guard-corps-affiliated-entities-charged
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1498.001/T1498.001.md
- https://learn.microsoft.com/en-us/azure/ddos-protection/ddos-protection-overview
- https://learn.microsoft.com/en-us/defender-endpoint/advanced-hunting-devicenetworkevents-table
- https://learn.microsoft.com/en-us/defender-endpoint/advanced-hunting-deviceprocessevents-table
- https://learn.microsoft.com/en-us/defender-endpoint/advanced-hunting-devicefileevents-table
Unlock Pro Content
Get the full detection package for T1498.001 including response playbook, investigation guide, and atomic red team tests.