T1498.001 CrowdStrike LogScale · LogScale

Detect Direct Network Flood in CrowdStrike LogScale

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.

MITRE ATT&CK

Tactic
Impact
Technique
T1498 Network Denial of Service
Sub-technique
T1498.001 Direct Network Flood
Canonical reference
https://attack.mitre.org/techniques/T1498/001/

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
#event_simpleName=ProcessRollup2
| FileName = /(?i)(hping3?|nping|trafgen|t50|loic|hoic|mhddos|ufonet|goldeneye|xerxes|udpflood|synflood|icmpflood|pyflood|rudy|packetsender|ostinato|netcat)/
  OR CommandLine = /(?i)(hping3?|nping|trafgen|t50|loic|hoic|mhddos|ufonet|goldeneye|xerxes|udpflood|synflood|icmpflood|pyflood)/
  OR CommandLine = /(?i)(--flood|-i\s+u0|--rand-dest|--rand-source|--syn.*--flood|--icmp.*--flood|--udp.*--flood|--faster|--turbo|--rate\s+\d{5,}|-c\s+\d{6,}|--count\s+\d{6,})/
| FloodToolMatch := if(match(FileName, regex="(?i)(hping3?|nping|trafgen|t50|loic|hoic|mhddos|ufonet|goldeneye|xerxes|udpflood|synflood|icmpflood|pyflood|rudy|packetsender|ostinato)")
    OR match(CommandLine, regex="(?i)(hping3?|nping|trafgen|t50|loic|hoic|mhddos|ufonet|goldeneye|xerxes|udpflood|synflood|icmpflood|pyflood)"),
    "true", "false")
| FloodArgMatch := if(match(CommandLine, regex="(?i)(--flood|-i\s+u0|--rand-dest|--rand-source|--syn.*--flood|--icmp.*--flood|--udp.*--flood|--faster|--turbo|--rate\s+\d{5,}|-c\s+\d{6,}|--count\s+\d{6,})"),
    "true", "false")
| SuspicionLevel := case(
    FloodToolMatch="true" AND FloodArgMatch="true", "Critical",
    FloodToolMatch="true", "High",
    FloodArgMatch="true", "Medium",
    "Low")
| select([timestamp, ComputerName, UserName, FileName, CommandLine, ParentBaseFileName, FloodToolMatch, FloodArgMatch, SuspicionLevel])
| sort(timestamp, order=desc)
high severity high confidence

CrowdStrike LogScale (Falcon Insight/Humio) detection for T1498.001 using ProcessRollup2 telemetry from the Falcon sensor. Matches known flood tool binary names and flood-specific command-line arguments. Assigns SuspicionLevel (Critical/High/Medium) based on combined presence of tool name and argument flags. Covers Windows, macOS, and Linux endpoints where the Falcon sensor is deployed.

Data Sources

CrowdStrike Falcon Insight EDR (ProcessRollup2 events)Falcon sensor on Windows, Linux, macOS endpoints

Required Tables

ProcessRollup2 (#event_simpleName=ProcessRollup2)

False Positives & Tuning

  • Falcon-protected endpoints used by network engineering teams where hping3, nping, or trafgen are installed as standard diagnostic tools and run under authorized change windows
  • Managed security service provider (MSSP) analyst workstations that have flood tool binaries present for detection validation or client incident reproduction
  • Development or build machines compiling or running network simulation tools (ostinato, packetsender) as part of automated testing pipelines — exclude by AgentIdList or sensor grouping tag
Download portable Sigma rule (.yml)

Other platforms for T1498.001


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 1UDP Flood with hping3 to Localhost

    Expected signal: Linux auditd: syscall execve for hping3 with argv containing '--udp', '--flood', '-p 53', '127.0.0.1'. Sysmon for Linux (if deployed): Process execution event with Image=hping3 and full CommandLine. Network metrics: High-volume UDP packet rate on loopback interface visible in netstat -s and /proc/net/udp. The -c 10000 flag limits total packets to prevent resource exhaustion.

  2. Test 2PowerShell UDP Packet Burst to Localhost

    Expected signal: Sysmon Event ID 1: Process Create for powershell.exe with CommandLine containing 'UdpClient', 'Send', 'Loopback'. Sysmon Event ID 3: High-frequency network connection events to 127.0.0.1:53 — this will generate thousands of Event ID 3 records in the Sysmon log. PowerShell ScriptBlock Log Event ID 4104 with full script content if ScriptBlock logging is enabled.

  3. Test 3ICMP Flood with ping -f to Localhost

    Expected signal: Linux auditd: syscall execve for ping with argv '-f', '-c', '10000', '127.0.0.1'. Process execution in syslog or Sysmon for Linux. Output shows packet statistics: '10000 packets transmitted, 10000 received, 0% packet loss'. Network metrics show ICMP packet rate spike on loopback interface visible via /proc/net/snmp ICMP counters.

  4. Test 4LOIC Flood Tool Binary Staging and Execution Simulation

    Expected signal: Sysmon Event ID 11: File Create event for %TEMP%\loic.exe — triggers the file-staging hunting query on flood tool binary name. Sysmon Event ID 1: Process Create for loic.exe with CommandLine '--method udp --target 127.0.0.1 --port 80 --threads 10'. Security Event ID 4688 (if command-line auditing enabled) with same process details. Sysmon Event ID 7: Image Load events showing DLLs loaded by the loic.exe process.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections