Every residential proxy exit is someone’s internet connection: a home router, a laptop, a phone on Wi-Fi. The software that makes that connection available to a proxy network has a name, proxyware, and it is the supply chain behind most of the residential market.
Understanding it helps anyone who buys residential proxies, and anyone who has been offered money to share their bandwidth. This guide explains how it works, where the line between a fair arrangement and an abusive one sits, and what can and cannot be checked from outside.
What proxyware is
Proxyware is software that runs on a device and relays traffic for a proxy network. When a customer of that network sends a request, it travels to the device, leaves through the device’s connection, and the response comes back the same way. The target site sees an ordinary home address, because that is what it is.
The device owner usually notices little. The software runs in the background, uses some bandwidth and some power, and in most designs stops when the device is busy, on battery or on a metered connection.
The term itself is neutral. Security researchers use it for this whole category of software, whether it was installed knowingly or not, which is part of why the word sometimes sounds more alarming than the technology is.
The two ways it reaches devices
Bandwidth-sharing apps. A person installs an app whose whole purpose is to share their connection, in exchange for a payout, usually per amount of traffic relayed. The deal is the product, so consent is about as clear as it gets. Payouts are modest, because a single home connection carries limited traffic and the network keeps most of the margin.
Software development kits inside other apps. A developer of a free app, game or browser extension includes a kit from a proxy network and is paid for each active user. In return, the user gets something: the app without ads, a premium feature, or simply the app for free. Here consent depends entirely on how the offer is presented. Some apps show a clear screen explaining that the device will share bandwidth and let the user decline. Others bury it in terms nobody reads.
Both routes can produce a legitimate pool. Both can also produce an illegitimate one.
Where consent holds and where it fails
The technology is the same in a fair and an abusive setup. What differs is how the person was asked and what protects them afterwards. A fair arrangement usually has:
- A plain consent screen that says the device will be used as an exit for other people’s traffic, shown before anything runs.
- Something real in return, stated up front.
- An easy way out that stops sharing at once, and uninstalling that removes the software fully.
- Limits that protect the owner, such as running only when idle, on Wi-Fi, or below a bandwidth ceiling.
- Controls on the other side, meaning the network vets its customers and refuses abusive uses, because those requests leave through someone’s home.
It fails when any of these is missing. The worst cases are not grey at all: security researchers have documented campaigns in which proxyware was installed alongside malware or pirated software without the owner’s knowledge. Those exits are compromised devices, not participants, and we cover that end of the market in the malware economy behind cheap residential proxies.
Most of the market sits between the two ends, which is why the sourcing questions matter.
What it means for the device owner
For someone thinking about sharing their connection, the trade is worth understanding in full.
- Traffic from strangers leaves through your address. If someone misuses the network, abuse reports and site challenges can land on your connection.
- Your internet provider’s terms may restrict reselling or sharing the connection, and data caps still apply.
- On phones and laptops, relaying traffic uses battery and data.
- You are trusting the network’s customer vetting, which you cannot see.
None of this makes sharing wrong. It makes it a decision that deserves informed consent, which is exactly the standard a fair network sets.
What it means for the buyer
If you buy residential proxies, the consent of the device owner is part of what you are buying, whether you think about it or not. Traffic through a compromised device is a legal and reputational risk that transfers to you, and a pool built on weak consent can shrink overnight when an app store removes the app that fed it.
Proxyware also explains a structural feature of the market. A single kit can be embedded in many apps, and a single network’s supply is often sold wholesale to many brands. That is why two providers can share a large part of the same exits, which Atlas measures on its proxy pool overlap page. It also explains why an IP pool is a population that comes and goes as devices sleep, switch networks or uninstall, rather than a fixed inventory.
What Atlas can see, and what it cannot
Measurement has a clear limit here, and it is worth stating plainly. Atlas sends requests and records what comes back. It cannot see the consent screen a device owner was shown, or whether one was shown at all.
What it can see are some consequences of sourcing: how much of one network’s pool appears in another’s, how many distinct exits a network shows over a window, and whether the exits are registered to consumer networks or hosting companies. Those are useful signals. They are not a sourcing audit, and we do not present them as one.
Atlas also has to behave well itself. Because every exit belongs to a real person, our testing ethics keep request rates deliberately low, restrict tests to read-only public pages, and never publish full exit addresses.
Questions to ask a provider
The full checklist for sourcing is in how providers ethically source residential IPs. For proxyware specifically, these five do most of the work:
- Do your exits come from a dedicated sharing app, a kit inside other apps, or both?
- What does the consent screen say, and can I see it?
- What do participants receive, and how do they stop?
- What limits protect the device owner’s connection, battery and data?
- How do you vet customers, and which uses do you refuse?
A provider with a fair supply chain can answer all five without hesitation. One that cannot is telling you something about its pool that no measurement will show.