Combatting Exit IP Fingerprinting: Mullvad's Mitigation Rollout

For most VPN users, the assumption is simple: switching servers resets your digital footprint and breaks the link between your previous session and your current one. However, a subtle vulnerability in how exit IPs are allocated can undermine this anonymity, allowing observers to correlate users even as they hop between different VPN endpoints.

Recently, Mullvad announced a mitigation rollout to address "Exit IP fingerprinting," a technical challenge where deterministic patterns in IP allocation could potentially be used to link a user's activity across different servers. This move highlights a critical intersection between network infrastructure and user privacy.

The Problem: Deterministic Exit IP Allocation

While a VPN masks your home IP address, it assigns you an "exit IP"—the address the rest of the internet sees. In many VPN configurations, the way these exit IPs are assigned is not truly random. If the allocation process is deterministic, an adversary monitoring traffic across multiple VPN servers could identify patterns.

As one community member noted on Hacker News, the danger isn't that a single IP exposes your identity, but that the relationship between IPs does:

"Most people think switching VPN servers completely resets correlation, but subtle infrastructure patterns like deterministic exit-IP allocation can still create linkage signals without actually exposing identity."

This means that if a user moves from Server A to Server B, and the exit IP they receive on Server B is mathematically or logically linked to the IP they had on Server A, a sophisticated observer can conclude that the same user is behind both connections.

The Mitigation Strategy

To combat this, Mullvad is rolling out a new mitigation system across its server fleet. The goal is to break the deterministic link between the user's internal VPN identity and the external IP address assigned to them at the exit node.

Currently, the rollout has reached several key servers globally, including:

  • North America: Dallas (us-dal-wg-701), Los Angeles (us-lax-wg-002), New York (us-nyc-wg-601), Salt Lake City (us-slc-wg-303), and Montreal (ca-mtr-wg-302).
  • Europe: Frankfurt (de-fra-wg-103), Paris (fr-par-wg-101), Dublin (ie-dub-wg-101), Oslo (no-osl-wg-101), Stockholm (se-sto-wg-208), and Helsinki (fi-hel-wg-201).
  • Asia-Pacific: Melbourne (au-mel-wg-402) and Sydney (au-syd-wg-001).

Broader Privacy Implications

The discussion surrounding this rollout has sparked a wider conversation about the limits of VPNs and the necessity of holistic privacy tools.

Beyond the Network Layer

Network-level anonymity is only one piece of the puzzle. Users are reminded that browser fingerprinting—which looks at screen resolution, GPU profiles, and device timing—can often bypass the anonymity provided by a VPN. Some users have suggested that the ideal solution is not just spoofing random data, but creating a "uniform" profile where every user looks identical to every other user, effectively hiding in a crowd of identical signals.

Alternative Approaches

For those seeking higher levels of isolation, the Mullvad Browser (which utilizes built-in proxies rather than standard WireGuard tunnels) offers an alternative. Specifically, its "Random mode" extension allows users to rotate IPs for each website they visit, further complicating any attempt at correlation.

Transparency as a Security Feature

One of the most praised aspects of this rollout is Mullvad's decision to document the issue publicly rather than silently patching it. In an industry where "security through obscurity" is common, this transparency allows the community to audit the mitigation and understand the actual risks of correlation attacks.

As one observer put it:

"The fact that Mullvad openly documented it instead of silently patching it is probably the best part here."

By treating the rollout as a public technical disclosure, Mullvad reinforces the idea that privacy is not a static product, but a continuous process of identifying and mitigating subtle leakage vectors.

Sources