SERVICER — Attack methods
Nineteen reviewed traffic methods: UDP, TCP, ICMP, GRE and cleartext HTTP over TCP. Stop controls and HTTP requests disabled by the native TLS gate are excluded.
- UDP payload floodVector 0
Sends repeated UDP datagrams containing random or zero-filled payload bytes, with a default length of 512 bytes. No application protocol is constructed.
- TCP state-seeded floodVector 1
Opens a TCP connection to obtain connection state, then sends crafted IPv4/TCP packets with payload using the observed ports and sequence state. ACK and PSH are enabled by default.
- TCP configurable flagsVector 2
Sends crafted IPv4/TCP packets with MSS, SACK, timestamp and window-scale options. Six configurable TCP flags default to off.
- TCP ACK with payloadVector 3
Sends crafted IPv4/TCP packets with ACK enabled by default and a generated payload, normally 512 bytes. Flags, ports and sequence values are configurable.
- TCP SYN with unsafe payloadVector 4
Attempts to send crafted TCP SYN packets with TCP options and payload. A buffer overflow in this ARM handler can corrupt memory and prevent transmission.
- UDP random and literal pairVector 5
Sends pairs of UDP datagrams: a random or zero-filled block followed by stored literal slash-x text. The text is not decoded hexadecimal or a demonstrated application exchange.
- UDP stored template attemptsVector 6
Sends stored request-shaped templates over UDP, including SSDP and binary DNS/SNMP/LDAP-like material. Truncation and invalid pointer behavior mean valid reflection exchanges are not established.
- UDP random hexadecimal textVector 7
Sends repeated UDP datagrams containing 1–1,400 random ASCII hexadecimal characters from 0123456789ABCDEF. No additional application protocol is constructed.
- TCP Xmas flagsVector 8
Sends crafted IPv4/TCP packets with FIN, PSH and URG set. Optional payload contains random or zero-filled bytes.
- TCP tiny random writesVector 9
Opens TCP connections and repeatedly sends 1–5 printable random characters, reconnecting after failures. No HTTP request is generated; a socket-array allocation defect may prevent execution.
- TCP connection holdingVector 10
Opens and holds TCP connections, monitors connection errors and reconnects after failures. It sends no HTTP headers or body; a socket-array allocation defect may prevent execution.
- TCP connect and closeVector 11
Repeatedly attempts TCP connections and immediately closes each socket. A configurable send timeout does not establish a delay between attempts.
- UDP RTP-shaped burstsVector 13
Sends UDP bursts with RTP-shaped headers, changing sequence numbers, timestamps and synthetic media payloads. Authenticated Discord voice or SRTP negotiation is not established.
- TCP randomized flags and dataVector 14
Sends crafted IPv4/TCP packets with randomized flags, sequence and acknowledgment numbers, and random payload. No XOR application framing is constructed.
- ICMP echo with payloadVector 15
Sends raw IPv4 ICMP Echo Requests with identifiers, incrementing sequences and generated payload. The default ICMP length is 56 bytes, including its header.
- GRE carrying IPv4/UDPVector 16
Sends GRE packets containing inner IPv4/UDP headers and random payload. The outer IP protocol is GRE, even though the raw socket is created with a TCP protocol value.
- GRE carrying Ethernet/IPv4/UDPVector 17
Sends GRE packets containing generated Ethernet and inner IPv4/UDP headers with random payload. Ethernet addresses are randomized.
- HTTP GET/POST keep-aliveVector 18
Sends repeated cleartext HTTP/1.1 GET or POST requests over TCP with Host, User-Agent and keep-alive headers. HTTPS URLs or a nonzero secure option return without traffic; no TLS client is implemented.
- UDP paced burstsVector 19
Sends short UDP bursts of random or zero-filled payload and sleeps between bursts. Defaults are three datagrams per burst and a two-millisecond delay.
Last 30 days