Skip to content
kryptonservers

DDoS protection for IPTV panels

Floods are dropped in the network card. On top of that, the guard reads player_api calls, stream paths and MAC portal requests, so it can tell a paying player from a cracker.

Six attacks IPTV panels get, and what stops each one.

L4

SYN and ACK floods at the panel's port

Every listener port, including 25461, 8080 and 2082, answers new connections with a cookie from XDP. Spoofed floods never open a socket on your panel.

L7

player_api.php and get.php floods

Request floods from scripts and bots are counted per address. Past the limit the address is banned in the proxy, then in the network card, in about a quarter of a second.

Accounts

Credential stuffing

One address trying many usernames on player_api, panel_api, get.php or xmltv.php is caught after a handful of attempts and banned globally.

Portals

MAC cracking on Stalker portals

An address cycling MAC addresses against your portal is recognised from the portal requests themselves and banned before it walks your MAC range.

Abuse

One account, a hundred viewers

Account sharing shows up as one line used from too many addresses at once; the account is blocked for a while instead of your whole panel slowing down.

Scans

Scanners and probes

Clients that collect 404s or switch user agents to slip past filters raise their score and get banned. Your access logs stay readable.

An attack on a panel, replayed in our lab.

We replayed a mixed attack against a proxied panel on a pair of dual Xeon servers: 15 addresses flooding requests, 15 trying usernames, 10 cycling MAC addresses and 10 scanning for pages, alongside 100 normal players and a whitelisted source at 196,000 requests a second.

  • Every attacker was banned: floods in 0.24–0.33 s, credential stuffing and MAC cracking within 1.3 s, scanners within 16 s.
  • No player was banned: 72,000 player requests, all served, slowest 1 % under 6 ms.
  • The bans reached the network card: from then on the attackers' packets were dropped in XDP, before the kernel.

The full write-up, method included, is on the technology page.

guard report

flood banned 15/15 first ban 0.24 s

creds banned 15/15 first ban 0.32 s

mac banned 10/10 first ban 0.37 s

scanner banned 10/10 first ban 12.6 s

legit banned 0/100 72,000 req · 0 errors

trusted banned 0/1 23.5 M req · 0 errors

Shield M is what most panels pick.

It turns on the IPTV detectors and fits several panels.

Shield S

One panel or site, hidden and filtered.

€19/ month

Protected services
1
Domains
3
Clean traffic
100 Mbps
Origins per service
2
  • XDP filtering in the NIC driver, before the kernel
  • SYN challenge on every listener port
  • L7 guard: floods, scanners, credential stuffing
  • TLS termination and automatic certificates
  • Health checks and reloads without dropped requests
Order on Telegram
Most chosen

Shield M

IPTV panels and busy APIs, with the IPTV detectors on.

€49/ month

Protected services
3
Domains
10
Clean traffic
500 Mbps
Origins per service
5
  • XDP filtering in the NIC driver, before the kernel
  • SYN challenge on every listener port
  • L7 guard: floods, scanners, credential stuffing
  • TLS termination and automatic certificates
  • Health checks and reloads without dropped requests
  • IPTV detectors: MAC cracking, account sharing
  • Custom L7 rules
Order on Telegram

Shield L

Several panels, more traffic, priority answers.

€99/ month

Protected services
10
Domains
Unlimited
Clean traffic
1 Gbps
Origins per service
10
  • XDP filtering in the NIC driver, before the kernel
  • SYN challenge on every listener port
  • L7 guard: floods, scanners, credential stuffing
  • TLS termination and automatic certificates
  • Health checks and reloads without dropped requests
  • IPTV detectors: MAC cracking, account sharing
  • Custom L7 rules
  • Priority support
Order on Telegram

IPTV panel protection.

Does it work with Xtream UI, XUI.one and similar panels?

Yes. The detectors read the request shapes these panels share: player_api.php, panel_api.php, get.php, xmltv.php, /live/user/pass/ stream paths and MAC portal requests. Nothing has to be installed on the panel.

Will my legitimate players be banned?

Thresholds are set per service and tuned with you. In our tests 100 legitimate addresses kept full access while 50 attacking addresses were banned, and a heavy whitelisted source stayed untouched. Resellers and your own servers can be whitelisted.

Can I protect the streams, not only the API?

Yes. Stream paths go to their own origin pool, so a flood on the API does not starve the streams, and long-lived connections survive our reloads.

Do I keep my ports?

Yes. Keep 25461, 80, 8080 or whatever your players use; every port you list is protected automatically and everything else is dropped silently.