New UDP Methods for MHDDOS

This update introduces three new Layer 4 UDP flood methods to the MHDDOS project. Each one is designed to target specific platforms or protections, using advanced spoofing and payload randomization techniques.

1. FIVEM-TOKEN

Purpose:
Simulates traffic typical to FiveM servers by flooding UDP with token-based authentication payloads.

Implementation details:

• Generates a random UUID token and a SteamID-like guid within valid ranges.
• Encodes them into an HTTP-like query string: token=...&guid=...
• Sends via UDP socket repeatedly to the target.

Effect:
Floods the target with seemingly valid authentication requests to stress token validation systems.

2. DISCORD

Purpose:
Targets Discord servers or similar UDP-based services by sending spoofed UDP packets with randomized payloads.

Implementation details:

• Constructs raw IP packets with spoofed source IPs (__ip__).
• Uses random UDP source ports in the range 32768–65535.
• Payload is 40 bytes of fully randomized binary content.

Effect:
Creates a high-rate UDP flood with unpredictable content to saturate bandwidth or processing power.

3. OVH-UDP

Purpose:
Bypasses OVH’s game server protections and WAFs by sending complex UDP packets containing fake HTTP-like headers and randomized binary payloads.

Implementation details:

• Each cycle sends 2–4 spoofed UDP packets.
• Randomizes the HTTP method: PGET, POST, HEAD, OPTIONS, PURGE.
• Randomly selects obfuscated paths such as:
  • /0/0/0/0/0/0
  • \\0\\0\\0\\0\\0\\0
  • /null
  • /%00%00%00%00
• Payload size varies from 1024 to 2048 bytes, generated with randbytes.
• Final payloads are encoded with latin1 and inserted into spoofed raw IP/UDP packets.

Effect:
Produces diverse, hard-to-detect UDP traffic resembling malformed or semi-legitimate requests, ideal for bypassing deep packet inspection and OVH filtering.

All implementations follow the project’s existing structure and support proper threading, spoofing, and stat tracking.