Sarbot — Attack methods

• Connected UDP payloadsVector 0

  Connected UDP payloads. Repeatedly sends generated or supplied payload bytes on connected UDP sockets to selected target addresses/ports.

• UDP datagramsVector 1

  UDP datagrams. Uses connected UDP when unprivileged or raw IPv4/UDP packet construction when the privilege branch is available; repeatedly sends payloads.

• TCP SYN packetsVector 2

  TCP SYN packets. Builds raw IPv4/TCP packets with SYN set, randomized fields and TCP options. Nonprivileged branch falls back to connected TCP payload handling.

• TCP ACK payloadsVector 3

  TCP ACK payloads. Builds raw IPv4/TCP packets with ACK set and generated or supplied payload bytes; connected TCP fallback is separate.

• TCP SYN/options and fast-open pathVector 4

  TCP SYN/options and fast-open path. Builds SYN packets with TCP options in the raw branch; alternate stream-socket branch uses sendto with the TCP fast-open flag and payload bytes.

• TCP connection-assisted packetsVector 5

  TCP connection-assisted packets. Opens TCP connections and uses a raw TCP receive/send path to construct further packets; connected TCP fallback is separate. Exact sequence tracking remains unvalidated.

• IPv4 protocol/header mismatchVector 6

  IPv4 protocol/header mismatch. Opens a raw UDP socket but sets the generated outer IPv4 protocol byte to 4 and the inner IPv4 protocol byte to UDP (17), then writes its payload. Treat as IP-in-IP-labelled/malformed-capable traffic, not a proven valid UDP flood; runtime wire validity is unresolved.

• GRE encapsulated UDPVector 7

  GRE encapsulated UDP. Builds an outer IPv4/GRE header followed by an inner IPv4/UDP packet and generated payload, then repeatedly sends raw packets.

• ICMP requestsVector 8

  ICMP requests. Constructs ICMP packet/header payloads for the destination, using a raw socket with datagram ICMP alternatives depending on build/privileges. Do not infer reflection from this code.

• Connected TCP payloadsVector 9

  Connected TCP payloads. Maintains a pool of nonblocking TCP connections and repeatedly writes generated or supplied payload bytes; reconnects on failure.

• TCP SYN packetsVector 10

  TCP SYN packets. Builds IPv4/TCP packets with SYN set and other basic flags cleared, then sends repeatedly. Its handler is distinct from ID 2; no unsupported service-specific label is assigned.

• UDP packet variantVector 11

  UDP packet variant. Sends UDP payloads with privilege-dependent raw/connected paths; preserves this distinct native slot without assigning an unproven amplification protocol.

• UDP header/payload variantVector 13

  UDP header/payload variant. Constructs raw IPv4/UDP packets using target and option data and repeatedly sends them. Additional option semantics remain open.

• TCP ACK packetsVector 14

  TCP ACK packets. Builds IPv4/TCP ACK packets with the other basic flags cleared; uses the connected TCP fallback when the raw branch is unavailable.

• UDP structured payloadsVector 15

  UDP structured payloads. Constructs repeated raw or connected UDP payloads with a structured/static prefix and variable data. A Source Engine marker alone does not prove an amplification attack.

• HTTP GET requestsVector 16

  HTTP GET requests. Repeatedly sends browser-style HTTP/1.1 GET requests over TCP with configured host/path and optional user-agent/cookie/referer values.

• TLS HTTP/2 requestsVector 17

  TLS HTTP/2 requests. Performs a TLS handshake over TCP, writes the HTTP/2 connection preface/settings, then sends header blocks on increasing odd stream IDs. Live negotiation and server acceptance are unverified.

• TLS HTTP request variantsVector 18

  TLS HTTP request variants. Performs TLS over TCP and selects HTTP/1.1 writes or HTTP/2 header-frame generation with varying path/headers. Browser-looking values do not establish challenge bypass.

Last 30 days