Attackers Hijacked Over 300 Tor Exit Relays to Intercept SSH Connections
Overview
In early October, attackers gained control of over 300 Tor exit relays, manipulating them to intercept SSH connections. This allowed them to redirect users’ traffic to malicious servers that captured login credentials. The attack specifically targeted SSH logins made through Tor from October 1 to 5, meaning anyone who logged in during that period could have had their password stolen. This incident raises serious concerns about the security of users relying on Tor for anonymity, as it shows how vulnerable even seemingly secure connections can be. Users need to be aware of this threat and consider additional protective measures when accessing sensitive services through Tor.
Key Takeaways
- Active Exploitation: This vulnerability is being actively exploited by attackers. Immediate action is recommended.
- Affected Systems: Tor exit relays, SSH servers
- Action Required: Users should avoid logging into SSH servers through Tor until further security measures are confirmed.
- Timeline: Newly disclosed
Original Article Summary
Attackers took control of more than 300 Tor exit relays in early October and used them to redirect SSH connections to servers that stole login passwords, a researcher found. Exit relays are the last hop in a Tor circuit, where traffic leaves the network for its destination. Only a password login to an SSH server made through Tor between October 1 and 5, after accepting the interception
Impact
Tor exit relays, SSH servers
Exploitation Status
This vulnerability is confirmed to be actively exploited by attackers in real-world attacks. Organizations should prioritize patching or implementing workarounds immediately.
Timeline
Newly disclosed
Remediation
Users should avoid logging into SSH servers through Tor until further security measures are confirmed. Implementing two-factor authentication on SSH accounts can also help mitigate risks.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.