Industry

Attackers Hijacked 333 Tor Exit Nodes to Intercept SSH and Email Traffic

A coordinated attack compromised over 300 Tor relays in October 2026, redirecting SSH connections and blocking encrypted email protocols to capture plaintext credentials and messages.

Last verified:

SSH Redirection and Email Protocol Blocking

Attackers who hijacked 333 Tor exit nodes in early October 2026 deployed a two-pronged interception strategy targeting both remote access and email services. According to Ars Technica, the campaign actively ran from October 2 to October 5, redirecting SSH connections to 12 attacker-controlled servers while simultaneously blocking encrypted email ports (25, 465, 587, 993, 995) on the compromised relays.

Tor users whose traffic exited through one of the 333 infected nodes would encounter SSH host-key mismatch warnings. Those who proceeded past the alert would unknowingly transmit their SSH credentials to attacker infrastructure. For email, the hostile configuration allowed unencrypted ports while filtering encrypted variants, creating conditions for downgrade attacks—though Ars Technica clarifies that whether such negotiation failures actually occurred remains unknown.

Initial Compromise: Late August, Persistence Through October

The attack unfolded in two phases. According to the Ars Technica report, the initial compromise began in late August when an attacker used a valid reused password to access a Tor management server. The attacker then installed Ebury, a Linux backdoor discovered 12 years prior, to maintain access.

By exploiting this foothold, the attacker pivoted to a second Tor infrastructure server called Switzerland2 via SSH, using an RSA key investigators could not locate in Switzerland2’s authorized_keys file—a technical inconsistency the report notes remains unexplained. Once Switzerland2 fell under attacker control, Ebury was installed there as well. This second-stage compromise gave the attacker the ability to reconfigure settings across the 333 downstream exit nodes.

Credential Hygiene and Detection Challenges

Investigators have not yet established the complete attack chain—specifically, how the attackers gained administrative control of all 333 underlying servers hosting exit relays. According to Ars Technica, the initial breach exploited password reuse, a basic credential management failure that cascaded through multiple layers of Tor infrastructure.

A researcher using the pseudonym Kaba, who contributed to the incident analysis, experienced the attack firsthand on October 6, describing how encrypted traffic passed through normally while SSH connections were transparently redirected. The selective nature of the redirection—targeting specific protocols while preserving others—suggests deliberate configuration rather than a widespread vulnerability.

Why This Matters

Tor relay operators must immediately audit SSH key distribution across all infrastructure servers and enforce unique, high-entropy credentials for each host. The reuse of a single password to compromise a management server demonstrates that centralized authentication weaknesses can grant adversaries control over hundreds of downstream relays.

Users running critical services—particularly SSH-based administration or email retrieval—over Tor should treat host-key-changed warnings as fatal connection events, not dismissible alerts. The October 2026 incident shows that such warnings reliably indicate active interception. Organizations dependent on Tor for infrastructure access should consider supplementary authentication mechanisms (hardware keys, certificate pinning) to reduce credential exposure if exit-node compromise occurs.

Frequently Asked Questions

How did attackers gain initial access to the Tor infrastructure?

According to Ars Technica, the attacker exploited a reused password to access a Tor management server in late August 2026, then installed the Ebury backdoor—a 12-year-old Linux rootkit—to maintain persistence.

What was the scope and timeline of the active hijacking campaign?

333 Tor exit relays were compromised and actively used to intercept traffic from October 2 to October 5, 2026. The initial compromise of the management infrastructure occurred earlier, in late August.

Did the attackers successfully capture plaintext email messages?

The attackers blocked encrypted email protocols on the hijacked exit nodes to force downgrade to unencrypted channels, but Ars Technica reports it remains unclear whether any downgrade attempts actually succeeded.

What SSH interception method did the attackers use?

SSH traffic was redirected to 12 attacker-controlled interceptor servers. Users who proceeded past host-key-changed warnings would unknowingly enter credentials into the attacker infrastructure.

#tor #security #ssh #email #infrastructure #backdoor #exit-nodes