In a concerning development for federal cybersecurity, security researchers have uncovered evidence that multiple computers connected to the White House network are being utilized as residential proxy exit nodes. This discovery, which highlights the pervasive and often invisible nature of modern proxy-based botnets, suggests that devices inside the Executive Office of the President may have been inadvertently enrolled in commercial proxy networks, potentially allowing third parties to route malicious or obfuscated traffic through the heart of the U.S. government’s digital infrastructure.
According to a detailed analysis by Layer3 Intel, six distinct IP addresses associated with AS2650—a network specifically reserved for the Executive Office of the President—were actively used by 28 different residential proxy services between October 5 and November 3. The firm’s findings indicate that the scale of this unauthorized usage is not merely incidental. "Our residential proxy enumeration pipeline exited through the White House network 236 separate times," Layer3 Intel reported in its technical blog post. These findings raise significant questions regarding the security protocols governing endpoint devices connected to highly sensitive government networks.
Residential proxy services, which are increasingly popular among digital marketers, data scrapers, and malicious actors alike, function by routing internet traffic through a network of everyday residential devices. By masquerading as legitimate home users, individuals can bypass geo-blocking, evade IP-based rate limiting, and mask their true digital footprint. When a device—such as a desktop computer or laptop—is infected with a software development kit (SDK) or an application that includes proxy-sharing functionality, it effectively becomes a gateway for anyone willing to pay a subscription fee to the proxy provider. In this scenario, any person who signs up for one of the identified public residential proxy services could, in theory, send requests through the White House network, effectively utilizing the prestige and perceived legitimacy of an Executive Office IP address.
The patterns identified by researchers provide a compelling narrative about the nature of the infection. Layer3 Intel observed that the majority of the unauthorized traffic occurred in the evenings, typically between 5:00 p.m. and midnight Eastern Time, with virtually no activity detected during the early morning hours. This specific cadence is highly suggestive of human activity rather than a public-facing guest Wi-Fi network. The researchers noted that the pattern points toward an individual who is regularly present on the White House network late into the evening, whose specific device has been compromised or inadvertently enrolled in a proxy SDK.
Further technical analysis conducted by the cybersecurity startup Synthient, which specializes in the identification and tracking of residential proxies, VPNs, and bot infrastructure, has helped clarify the mechanism behind this activity. According to Synthient, the traffic was traced to Windows 11 machines running the InfaticaSDK. Infatica, a Singapore-based provider of web-data intelligence and proxy services, markets itself as a legitimate provider of ethically sourced IP addresses, claiming a network of more than 45 million residential, mobile, and datacenter IP addresses worldwide.
The involvement of Infatica has drawn additional scrutiny due to the historical background of its leadership. As investigative journalist Brian Krebs has reported, Infatica’s founder, Vladimir Fomenko, is also the owner of King Servers, an IT infrastructure and web hosting provider. King Servers gained notoriety in the cybersecurity community after it was revealed that six of the eight internet addresses used by Russian state-sponsored hackers during the 2016 U.S. election interference operations were hosted by the company. While there is no evidence to suggest that the current proxy activity is tied to state-sponsored actors, the presence of such software on a network as sensitive as that of the White House underscores a broader vulnerability in how endpoint security is managed, particularly when employees or contractors inadvertently introduce third-party software that turns their machines into open relays.
The discovery serves as a stark reminder that the reach of residential proxy networks is virtually global. Layer3 Intel’s broader investigation into the extent of these networks revealed that they have infiltrated even the most remote and isolated regions of the planet. The firm documented that residential proxy exits have been observed in places as geographically distant as the South Atlantic territory of Saint Helena, Ascension, and Tristan da Cunha. In that specific region alone, the researchers recorded 413 unique addresses and over 32,000 observations, with the traffic split between the Starlink satellite network and the local internet provider, Sure Saint Helena.
The proliferation of these proxy exit points is not limited to the South Atlantic. Similar activity has been cataloged in various other remote outposts, including Antarctica, the Chagos Islands, the Falklands, Norfolk Island, Pitcairn, South Georgia, Svalbard, and Tokelau. This global footprint illustrates the effectiveness of the proxy business model: by incentivizing users to share their bandwidth or by bundling proxy SDKs into otherwise innocuous-looking applications, providers can maintain a massive, geographically diverse pool of IP addresses that are difficult for security teams to block without inadvertently disrupting legitimate traffic.
For organizations like the Executive Office of the President, the existence of these exit nodes on their internal network poses a unique challenge. While the proxy traffic itself may not represent a direct breach of sensitive data, it represents a failure of endpoint control and a significant risk to the network’s reputation and integrity. If devices within the White House can be turned into proxies, those same devices could potentially be used for other, more malicious purposes, such as unauthorized data exfiltration or as staging points for lateral movement within the network.
The security community has long warned about the risks associated with "shadow IT"—the use of unauthorized software, hardware, or services by employees. In the context of a high-security environment, the presence of a commercial proxy SDK on a Windows 11 machine is a quintessential example of this danger. Whether the software was installed by an employee looking to bypass regional content restrictions or was bundled with a seemingly benign third-party application, the result is the same: the machine becomes an unwitting participant in a global network, exposing the underlying infrastructure to external manipulation.
As security professionals continue to grapple with the rise of AI-linked breaches, increasingly sophisticated phishing campaigns, and the vulnerability of various kernel architectures, the "White House proxy" incident serves as a call for stricter endpoint configuration management. The ability of researchers to pinpoint the exact time and nature of this traffic suggests that while the proxy networks are designed to be stealthy, they are not invisible. For the White House, the focus will likely shift to auditing endpoint software, restricting the installation of third-party SDKs, and hardening the network against the unauthorized routing of traffic through its dedicated IP space.
This incident also highlights the ongoing tension between the legitimate, commercial use of residential proxies for market research and the inherent security risks they introduce when they operate without oversight. As the lines between legitimate utility and cyber-security risk continue to blur, agencies and corporations alike will need to become more aggressive in their monitoring and mitigation strategies. The fact that an IP space as sensitive as the Executive Office’s could be leveraged by a commercial proxy provider is a wake-up call, emphasizing that in a hyper-connected world, the security of a network is only as strong as the most poorly managed device connected to it.






