wireguard proxy, residential exits
each device gets a wireguard tunnel pinned to its own residential sticky session. no leaks, no sharing, no datacenter smell.
good evening
phone1 → 198.51.100.23 · up
test1 → 198.51.100.87 · up
residential, by design
policy routing ties each wireguard peer to its own tunnel and its own socks5 credentials. profiles never share an exit.
peer subnets have no route via the vps uplink. if a proxy dies, traffic drops — it cannot leak.
most residential socks5 is tcp-only. dns is converted to tcp through the same proxy; other udp is dropped. browsers just work.
dead location? pick another one. exits rotate regularly and new ones appear on their own.
locations span the residential network. pick the one you need and connect.
mullvad-style desktop client, proton-style builds, and an ops web panel. api underneath it all.
get running fast
download criminals proxy for windows or linux. no account signup page, no email — your login is handed to you.
one username, one password. the app connects to the private network automatically.
each location is a fresh residential exit. press connect — exit ip is residential from packet one.
getting started
windows (.msi) or linux (.deb, .appimage) from the releases page.
use the username and password you were given. nothing else to configure.
pick a location, press connect. done.
faq
no. everything leaves through a residential exit ip, and dns goes through it too. check any what-is-my-ip page while connected.
no. every location is its own sticky session — your exit is yours alone while you hold it.
yes, but each device needs its own login/location. ask for a second one and it takes seconds to create.
disconnect, wait a few seconds, reconnect. if a location stays dead, pick another one or ask — exits get rotated regularly.
browsing, streaming and most apps work fine. latency-sensitive udp gaming can lag — residential exits trade ping for legitimacy.