Spoofed at the socket
Source addresses are forged below the stack. No handshake, no ramp, no reply path to throttle.
Spoofed raw UDP, forged below the stack, fired from your own shell.
Our fleet, not a reseller
Every flood leaves a worker we run on dedicated KVM. Capacity is measured, never claimed.
Receipts per run
Each attack reports its own peak pps and bytes sent, live and in your history. You see what left.
telemetry
On the wire right now.
Everything your account is firing, refreshed every second. Attacks run from your shell — this page only watches.
Sign in to see your live floods.
Continue with Discordfire from your shell
ssh -p 2222 zshell@shell · then attack 1.2.3.4 --mc 120
plan—
concurrency—in use / allowed
today—attacks / quota
ceiling—max duration
Active
idle- nothing firing
the record
Every flood, on file.
Target, profile, duration, peak and bytes — kept so you can prove what hit and tune the next run.
Sign in to open your attack history.
Continue with DiscordAttacks
—| target | profile | duration | peak | sent | source | status | when |
|---|
pricing
Plans
Three days to test the net, or own it for life. Crypto only — pay here or with /buy in Discord. No subscriptions, no renewals.
invoice pending
—
—
—
Invoices lock for 15 minutes. Send the exact amount once, from any wallet. Credit applies when an admin confirms on chain.
What you get on both
Full profile list, spoofed UDP, 120 second ceiling, shell and API access. Lifetime simply raises concurrency, daily runs and tier access.
Paid by Discord
/buy in the server opens the same invoice privately. Your role and limits apply the moment it settles.
Before you pay
the honest bit- Delivery is instant. The invoice settles on chain and your concurrency, quota and roles rise on the next request.
- Quota is daily. It resets at 00:00 UTC. Unused runs do not roll over.
- Same account either door. Website and Discord share one login, one plan and one history.
- Tiers are honest. Solid profiles drop lobbies. Brutal ones are best-effort and badged as such — no promises we cannot keep.
firing line
One shell. Full control.
Floods never route through a browser tab. Add a key, open SSH, and the menu does the rest — or script the API.
Sign in to get your shell and API details.
Continue with DiscordConnect
one download, then double-clickWindows. Two files, no PuTTYgen, no manual host or port.
- download key saves to Downloads as
znet.ppk - download session double-click it once, then Yes
Then open PuTTY, double-click Z-Net in the saved list, and type your target IP when the menu asks. Done.
Already have PuTTY set up? Paste this instead:
putty.exe -ssh -P 2222 -i %USERPROFILE%\Downloads\znet.ppk zshell@shell
On macOS or Linux: ssh -p 2222 zshell@shell — add the key with ssh-add after converting it, or use /ssh add in Discord with your own key.
API
script itMint a key with /key create in Discord.
curl -H "authorization: Bearer $KEY" \
-d '{"target":"1.2.3.4","duration":60}' \
https://host/api/attack
Rules of the net
short list- One attack per target at a time — stacking the same IP splits your own ceiling.
- Home lines and game servers. Websites behind Cloudflare are supported, not promised.
- Duration is capped by plan. The worker holds the flood for exactly that long.
arsenal
Built for the lobby, not the homepage.
Each profile is a captured packet shape for a specific game port, tiered by what actually drops players. Headers are validated before a badge counts.
Profiles
Solid ships. Heavy is benched per provider until it proves out.