Home › Intelligence › Brief
BREACH BRIEF 🟠 High Breach

White House Devices Compromised as Residential Proxies, Enabling External Traffic Through Federal IPs

Researchers found that six White House IP addresses were being used as exit nodes by dozens of residential‑proxy services after Windows 11 workstations were infected with the Infatica proxy SDK. The incident demonstrates a lapse in endpoint security and network‑segmentation controls, raising audit‑readiness concerns for federal agencies.

Verisq™ Intelligence · 📅 November 06, 2026 · 📰 databreachtoday.com
Get the weekly threat digestBreaches, exploited vulnerabilities and advisories that matter to your vendors, every Friday. Free.
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
3 recommended
📰
Source
databreachtoday.com

White House Devices Compromised as Residential Proxies, Enabling External Traffic Through Federal IPs

What Happened — Researchers at Layer3 Intel discovered that between Oct 5 and Nov 3 2026, six IP addresses belonging to the White House network were repeatedly used as exit nodes by 28 commercial residential‑proxy services. The services routed traffic from the researchers’ own probes through those White House IPs hundreds of times, without any targeted probing of the network. A separate analysis by proxy‑detection firm Synthient identified the same pattern and traced it to Windows 11 workstations infected with the Infatica SDK – a proxy software development kit. The compromised devices appear to have been operated by staff members during evening hours, suggesting the SDK was installed locally and allowed the machines to act as open proxies.

Why It Matters for Trust & Control Assurance — The incident highlights a failure in endpoint security and network‑segmentation controls, underscoring the need for continuous monitoring of device configurations and strict access‑control policies.

Who Is Affected — Federal government agencies, specifically the Executive Office of the President; any organization that relies on unmanaged endpoint devices for sensitive communications.

Recommended Actions

  • Conduct an immediate inventory of all endpoint devices with external connectivity and verify that no unauthorized proxy SDKs are installed.
  • Enforce network segmentation and deploy outbound‑traffic monitoring to detect anomalous proxy use.
  • Review third‑party software procurement processes and require security‑by‑design assessments for any SDKs or libraries.

Source: DataBreachToday

Technical Notes

  • Attack vector: Malware‑based proxy SDK (Infatica) installed on Windows 11 workstations.
  • No public CVE; the compromise stems from malicious third‑party software rather than a known software flaw.
  • Data types: Not a data breach per se, but the proxy capability could enable lateral movement and data exfiltration.

Source: DataBreachToday

📰 Original Source
https://www.databreachtoday.com/white-house-ip-addresses-sold-through-proxy-services-a-33315 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Third-party risk

Does this breach reach you?

Verisq continuously monitors your vendors for breach and ransomware activity, so the question stops being whether it happened and becomes whether it reaches you.

See a live Trust Center →