On this page (8 sections)

Researchers at Layer3 Intel say that addresses on the White House network have been acting as exit points for residential proxy services. Anyone who pays a few dollars to a public proxy service could, in effect, send web requests that appear to come from inside the Executive Office of the President. The finding was reported on November 4 to 6, 2026.

There is no CVE and no vendor advisory behind this story, and no compromise of White House systems has been reported. It still matters to anyone who runs a network or a website, because the same mechanism, a proxy SDK bundled into an ordinary app, can turn any office PC into someone else's exit node.

What Layer3 Intel reported

According to Infosecurity Magazine, Layer3 Intel found the activity through its Residential Proxy Observatory. The firm says it did not target the network. Its staff were requesting ordinary global rotating access through proxy services when traffic exited through the White House address block.

Layer3 reports that its pipeline exited through the network 236 separate times, using six addresses on 26 of the 30 days between October 5 and November 3. It cross-checked the addresses against public lookup pages from Spur and Synthient, which independently flagged them as residential proxy exits, per Help Net Security.

Layer3 also noted that about half of the activity fell between 5 p.m. and midnight Eastern Time, with almost none in the early morning. It reads this as a person regularly on the network in the evening whose device carries a proxy SDK, rather than a public guest Wi-Fi network. That is an inference. Layer3 itself states that its data shows the exits, not the device or the person behind them.

What is confirmed and what is not

The exits themselves rest on Layer3's observations plus the cross-checks from Spur and Synthient. The identity of the software is a separate and weaker claim.

  • Synthient, one of the detection services, claimed that the traffic comes from Windows 11 machines running InfaticaSDK, per SecurityWeek.
  • A day later Synthient said it saw Windows 10 and 11 devices beaconing to proxy providers such as Geonode, Infatica and Mellowtel, and said with high confidence that the installed app is Rave.io, a shared streaming app it says bundles 12 proxy SDKs (Help Net Security).
  • These are Synthient's claims. The reports do not show confirmation from the White House, Infatica or the app's maker, and Infosecurity Magazine said it had contacted the White House for comment.
The three articles are separate reports of the same Layer3 research, not independent confirmation of each other. No original Layer3 post was available for this article, so details come from press coverage.

Why a proxy SDK on a work device is a problem

Residential proxy services sell access to everyday devices. A customer's traffic is relayed through the device so it looks like it comes from that device's home or office connection. Many such devices are enrolled through SDKs that app developers bundle into free apps, often with little visibility for the person who installed them.

For a site owner, this has two practical effects. Traffic from a trusted network can no longer be assumed to come from the people on it, so allowlisting an office or partner IP range is weaker than it looks. And the device acting as an exit node is a foothold inside the network: Layer3 cited Synthient research showing that poorly secured proxy SDKs can give outsiders access to internal networks and let them move laterally. It pointed to the Kimwolf botnet, which Synthient documented reaching at least two million devices, mostly Android devices with an exposed ADB service, through residential proxy networks.

Layer3's warning is conditional: if an SDK on the White House network had the same kind of flaw, anyone buying proxy access could use it to reach internal systems. No such flaw has been reported there.

Who is realistically exposed

  • Offices and agencies where staff install consumer apps (streaming, VPN, free utilities) on work laptops.
  • Organizations with BYOD or loosely managed Windows endpoints.
  • Teams that rely on IP allowlisting for admin panels, hosting dashboards, staging sites or APIs.
  • Any network that does not log or filter outbound connections from workstations.

How to check your own network

Start from the endpoint. You are looking for apps nobody approved, and for workstations making unexpected outbound connections. These read-only checks are a starting point, not proof that a device is clean.

On a Windows workstation, this lists installed programs by name so you can spot unapproved apps (run in PowerShell, review the output for anything unfamiliar such as shared-streaming or free VPN tools):

List installed programs from the registry (Windows, read-only)PowerShell
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*, HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, Publisher, InstallDate | Sort-Object DisplayName

To see which remote addresses a Windows machine is talking to right now, run the following in PowerShell. Look for many connections to unfamiliar hosts from a process you do not recognize:

Show established outbound TCP connections with process IDs (Windows, read-only)PowerShell
Get-NetTCPConnection -State Established | Select-Object LocalAddress, RemoteAddress, RemotePort, OwningProcess | Sort-Object RemoteAddress

On a Linux server or gateway, this lists established TCP connections and the processes behind them. Run it as root to see process names, and look for unexpected long-lived outbound sessions:

List established TCP connections with owning processes (Linux, read-only)Shell
ss -tnp state established

You can also look up your own public IP addresses on proxy-detection lookup pages such as those Layer3 used (Spur and Synthient). If one of your addresses is flagged as a residential proxy exit, treat a device behind it as suspect.

What to do now

  1. Inventory software on workstations and remove consumer apps that are not needed for work, especially free streaming, VPN and utility apps.
  2. Restrict software installation to administrators and use an application allowlist where you can.
  3. Review firewall or DNS logs for workstations contacting known proxy provider domains, and block them at the network edge.
  4. Do not treat office or partner IP ranges as proof of identity: require MFA and per-user credentials on admin panels, hosting accounts and staging sites.
  5. Segment guest, BYOD and workstation networks from servers and admin interfaces.
  6. Check your own public IPs against proxy-detection lookups and investigate any device behind a flagged address.
  7. If you find a proxy SDK, remove the app, scan the device, rotate credentials used on it and review what else it could reach.
Caution. Isolating or reimaging a workstation interrupts its user and any services it runs. Confirm what the device does before taking it offline, and keep logs and disk evidence if you may need an investigation.

Detection and monitoring afterwards

Keep outbound logging on. Unusual evening or weekend traffic from a workstation, many short connections to varied hosts, or a new background process phoning home are the signs to look for. For your public sites, watch for logins and admin requests arriving from addresses that are normally trusted, since a proxy exit makes hostile requests look local.

Layer3's chosen label for this is simple: the exits are visible from outside, but the infected device is only visible from inside. Outside checks, such as a free security headers check or monitoring for certificate and DNS changes on your domains, will not find a proxy SDK on an office PC, but they help you notice changes to the sites that attackers target next. For background on what outside scanning can and cannot see, read what outside-in malware detection can and cannot see.

Timeline

Key dates from the reporting
DateEvent
October 5 to November 3, 2026Layer3 records 236 exits through six addresses on AS2650
November 4, 2026Layer3 publishes its research; Synthient claims InfaticaSDK on Windows 11 machines; Layer3's founder says the latest activity was that evening
November 5, 2026Synthient says it believes the app is Rave.io, per Help Net Security
November 5 to 6, 2026Infosecurity Magazine, SecurityWeek and Help Net Security report the findings

Layer3 says it has backed up the raw logs and shared its findings with a US federal agency, per Infosecurity Magazine. Whether the activity has stopped was not confirmed in the sources.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. Researchers Find Residential Proxies on White House Networksecurityweek.com ·
  2. Residential proxy traffic caught leaving the White House network - Help Net Securityhelpnetsecurity.com ·
  3. Residential Proxy Traffic Traced to White House Networkinfosecurity-magazine.com ·
  • residential proxies
  • proxy SDK
  • Layer3 Intel
  • network security
  • botnets