SSL Stripping: How Malicious Tor Exit Nodes Exploit It

SSL stripping is a form of cyberattack where an adversary silently downgrades a secure, encrypted HTTPS connection into an insecure HTTP connection, enabling them to eavesdrop on or manipulate sensitive web traffic. When applied within the Tor network, malicious operators run compromised exit nodes to perform SSL stripping on unsuspecting users, intercepting unencrypted data—such as login credentials, session cookies, and personal communications—as it leaves the Tor network for the clearnet.

What is SSL Stripping?

SSL stripping, also known as an SSL downgrade attack, exploits the transition period when a user connects to a website. Often, a user types a generic domain name (e.g., example.com) without specifying the https:// protocol. Traditionally, the server responds with a redirect (such as HTTP 301 or 302) instructing the browser to upgrade the connection to HTTPS.

In an SSL stripping attack, a machine sitting in the middle intercepts this upgrade request:

1. The client requests an unencrypted connection to a website.
2. The attacker intercepts the request and establishes a legitimate, encrypted HTTPS connection with the destination server.
3. The server responds with HTTPS data to the attacker.
4. The attacker strips the encryption and delivers the plain HTTP version back to the client.

Because the browser continues communicating in plaintext HTTP, the attacker has complete visibility into all transmitted data, while the web server believes it is handling a secure session.

The Role of Tor Exit Nodes

The Tor network routes internet traffic through a series of three volunteer-operated relays: the guard node, the middle node, and the exit node. Layers of encryption protect the traffic as it travels through the first two nodes.

However, the exit node is the final relay in the circuit. Its job is to decrypt the outermost layer of Tor encryption and forward the request to the destination web server on the public internet. Consequently, the exit node acts as the local gateway between the Tor network and the clearnet, meaning it can see the traffic in whatever state it was sent—encrypted if using HTTPS, or completely unencrypted if using HTTP.

How Malicious Exit Nodes Execute SSL Stripping

While Tor hides a user’s IP address from destination websites, it does not automatically encrypt the contents of traffic beyond the exit node if the underlying web protocol is unencrypted. Malicious exit node operators exploit this position to execute SSL stripping attacks at scale:

• Intercepting Plaintext Requests: When a user accesses an HTTP site or requests a non-preloaded HTTPS site without specifying the protocol, the exit node intercepts the initial plaintext connection.
• Rewriting Traffic in Real Time: The malicious exit node creates a secure HTTPS tunnel to the target website on the user’s behalf but converts all HTTPS links and redirects on the received webpages into HTTP before sending them back into the Tor circuit.
• Harvesting Credentials and Modifying Data: Because the traffic between the user and the exit node is rendered in cleartext HTTP, the rogue operator can use automated packet-sniffing software to harvest passwords, session tokens, and cryptocurrency addresses, or even inject malicious scripts into the unencrypted web pages.

Defenses Against SSL Stripping on Tor

To protect against SSL stripping attacks from compromised exit nodes, modern browsers and network protocols rely on several defensive mechanisms:

• HTTP Strict Transport Security (HSTS): HSTS is a web server directive that forces browsers to only communicate over HTTPS. Preloaded HSTS lists built directly into browsers ensure that the browser never initiates an unencrypted HTTP request for participating domains.
• Tor Browser’s HTTPS-Only Mode: The Tor Browser includes built-in protections that automatically upgrade connections to HTTPS and actively block unencrypted HTTP connections unless explicitly overridden by the user.
• Using Onion Services: Navigating directly to Tor Onion services (.onion domains) eliminates the need for an exit node entirely. Onion-to-onion routing ensures end-to-end encryption across the entire Tor circuit, making exit-node-based SSL stripping impossible.