Re:Visualizing the locations of malicious login attempts
by micw on Friday April 26, 2024 @12:19AM
(#40165919)
"Failed publickey" - does this make sense? What is the chance to brute-force a private key that way?
[ Parent
| on HN ]
Re:Visualizing the locations of malicious login attempts
by magnat on Friday April 26, 2024 @01:01AM
(#40166089)
If you haven't updated your Debian in a while, 1 in 30000 apparently: https://www.hezmatt.org/~mpalmer/blog/2024/04/09/how-i-tripp...
Re:Visualizing the locations of malicious login attempts
by iforgotpassword on Friday April 26, 2024 @02:48AM
(#40166568)
1. Scrape GitHub et al for accidentally committed private keys, maybe even get the appropriate username.
2. Run botnet that tries all these keys on the entire Internet.
3. Profit!
Re:Visualizing the locations of malicious login attempts
by ykonstant on Friday April 26, 2024 @03:45AM
(#40166806)
Why is GitHub not(?) hosting a flock of repos* with fake private keys/username pairs to annoy/deter those people?
*Flock because of the Cloud? What is the appropriate noun for many repos?
Re:Visualizing the locations of malicious login attempts
by apstls on Friday April 26, 2024 @01:06AM
(#40166109)
It could be key spraying, maybe targeting a particular organization with distributed infrastructure for which the attacker already has some keys, but more likely groups blasting default keys (i.e. for some crappy IoT devices that included them in the firmware etc) for a nice & quick botnet.