this post was submitted on 20 Oct 2026
55 points (100.0% liked)

Pulse of Truth

2576 readers
132 users here now

Cyber Security news and links to cyber security stories that could make you go hmmm. The content is exactly as it is consumed through RSS feeds and wont be edited (except for the occasional encoding errors).

This community is automagically fed by an instance of Dittybopper.

Commenting rules:

founded 3 years ago
MODERATORS
krogoth@infosec.pub
55
How I got over 300 Tor exit nodes removed (kaba.cx)
submitted 2 days ago by lemmydev2@infosec.pub to c/pulse_of_truth@infosec.pub
1 comments fedilink hide all child comments
 

On Friday Oct 2, 09:35am, 333 infected exit nodes started a coordinated campaign to intercept SSH connections and gather as much unencrypted data as possible.

To give you a sense of scale, all of Tor has around 3000 exit relays, so roughly 10% were under their control.

The attackers had gained access to the servers two months earlier, in August, and quietly deployed their Ebury 1.8.3 payload (an OpenSSH backdoor and credential stealer for Linux).

you are viewing a single comment's thread
view the rest of the comments
[–] hirihit640@sh.itjust.works 1 points 1 day ago

reposting what I commented in another thread:

SSH MitM attacks are very easy to pull off. To secure yourself, use key authentication instead of passwords, and don't ignore the warning that SSH will give you saying "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED".

If you are using something like Tails, you will need to make sure to persist the ssh hosts key file (~/.ssh/known_hosts), or else you will not not be warned when a MitM attack is being performed.

More discussion here: https://news.ycombinator.com/item?id=50166257