Show HN: Watch bots interact with an SSH honeypot in real time
11–20 of 75 posts
Re: Show HN: Watch bots interact with an SSH honeypot in real time
#12Hi HN, I maintain several web servers and kept seeing a constant stream of SSH login attempts. At some point I became curious: what do these bots actually try to do after they get in? I set up a Cowrie SSH honeypot and built a small live dashboard around its JSON logs. Cowrie listens on port 22, a Python service follows the log and streams events over WebSockets, and Nginx serves the frontend. The whole thing current…
Some kind of source IP masking would be prudent. As you pointed out, some of those machines are compromised, and you aren't making their owners' lives any easier. Bad actors might use the data you're publishing to fingerprint specific exploits to which the machines are vulnerable, multiplying the problem. If producing an IP blacklist is one of your aims, divorcing it from any specific traffic would be more responsibl…
Hard for me to find much sympathy for negligent users who unintentionally allowed their home computers or phones to join a malicious botnet, or their ISPs who aren't stopping the activity. Even if it is my own grandma's PC.
I agree about the content though, there probably are a lot of actually innocent victims' personal information in the traffic itself.
Re: Show HN: Watch bots interact with an SSH honeypot in real time
#13Earlier quoted context omitted.
Hi, this is very interesting, thanks. While trying to educate myself about honeypots I came across this ( https://securehoney.net/ ). The aggregations of popular logins and IP locations seem interesting.
From that site: Files uploaded 25,522 (46 unique) Malware uploaded 7,735 (43 unique) I wonder what 3 files were so common that they were uploaded 17,787 times instead of malware.
Re: Show HN: Watch bots interact with an SSH honeypot in real time
#14Re: Show HN: Watch bots interact with an SSH honeypot in real time
#15Earlier quoted context omitted.
Some kind of source IP masking would be prudent. As you pointed out, some of those machines are compromised, and you aren't making their owners' lives any easier. Bad actors might use the data you're publishing to fingerprint specific exploits to which the machines are vulnerable, multiplying the problem. If producing an IP blacklist is one of your aims, divorcing it from any specific traffic would be more responsibl…
> Some kind of source IP masking would be prudent. As you pointed out, some of those machines are compromised, and you aren't making their owners' lives any easier. Hard for me to find much sympathy for negligent users who unintentionally allowed their home computers or phones to join a malicious botnet, or their ISPs who aren't stopping the activity. Even if it is my own grandma's PC. I agree about the content thoug…
Re: Show HN: Watch bots interact with an SSH honeypot in real time
#16Re: Show HN: Watch bots interact with an SSH honeypot in real time
#17Looks cool!