You can use IPinfo's IP map (<a href="https://ipinfo.io/tools/map" rel="nofollow">https://ipinfo.io/tools/map</a>) or IP summary tool (<a href="https://ipinfo.io/tools/summarize-ips" rel="nofollow">https://ipinfo.io/tools/summarize-ips</a>).<p>Both of these services support sending IP addresses via an API endpoint and can handle up to 500k IP addresses. You can also share the report via URL.
I always wondered how the IPs like this 180.101.88.232 from this block:<p>ISP ChinaNet Jiangsu Province Network
Domain Name chinatelecom.com.cn<p>Continue to be the source of thousands of ssh password login attempts for years and years on end.<p>It's not a big deal, I use a tarpit on all ssh with 2FA on the one I use, but it seems ridiculous that some participants of the internet don't give a shit about the rest of the world.
It's been a couple decades since I adminned servers and firewalls. In my experience, in the early 2000's, Russian IPs were extremely common. I was surprised that OP didn't see even one. Can anyone conjecture on what might account for the apparent change?
These kinds of experiments get even more interesting when you also pipe the IPs into Shodan and find out that a lot of the malicious login attempts are coming from pwned DVRs and other devices.
> Upon closer inspection of Asia, we can notice a significant number of addresses located in South Kora, (and possibly North Korea?), as well as in Taiwan.<p>> I was surpised to see that the distribution of attacks is extremely uneven with most of it concentrated in parts of Asia, Europe, and the US, and (almost) none from South America, Middle East, and Russia.<p>Aside from the casual stereotyping of bad actors here, the article completely neglects the fact that just because the attack is sourced from a certain IP/geolocation doesn't mean that the attacker resides in that location.<p>What you most likely have is a listed of pwned PCs with fast internet connections being used in botnets.
I always install fail2ban on publicly exposed machines, especially if ssh is enabled. It won't block new malicious IPs but at least it will stop bruteforce attacks coming from each IP
Fun. You could also try putting the data into Google's data studio (now looker) to visualize them in an interactive map you can publish. Add things like size of dot corresponding to number of attempts, add reverse DNS/whois info to the info bubble, etc. Wonder how much came from residential vs business ip space.<p><a href="https://lookerstudio.google.com" rel="nofollow">https://lookerstudio.google.com</a>
> Interesting! We can see the most locations in India, Indonesia, and China as well as a significant number in the US and Europe.<p>Are these because the bad guys are in there or just because of the population size?<p>China, India, US, and Indonesia are the top four of the most populous country and also 4 countries with most internet users.<p>Even the size of 10% of Indonesian internet users are almost the entire Taiwan population.
A few years ago I've built a more simple visualization similar to this one with the attacks on the host the application was already deployed: <a href="https://github.com/ludovicianul/geolog">https://github.com/ludovicianul/geolog</a>. China was mostly leading, but there were many from US and Europe.
Holy moly! That explains why I frequently get captcha when using residential internet in Jakarta. I don't see those captcha when accessing from e.g. Kuala Lumpur or Singapore.<p>Is the information in the article actionable? E.g. can I complain to someone with authority?
As others have pointed out, the location of the IP address does not necessarily correspond with the location of the attackers.<p>Specifically, in Germany, the central-ish culster of dots is in the Frankfurt area, which is also the location of DE-CIX, one of the world's largest internet exchange points, and of roughtly 1/3 of all datacenters in Germany.<p>So I think rather than comparing the IP locations with population density, it would be even more interesting to compare them with the location of internet infrastructure. This is of course correlated, and probably harder to find as an open dataset.
This was cool. The makings of an adhoc DIY cyber intelligence dashboard.<p>I guess the distribution could reflect places with lower income levels looking to get free compute? (for whatever purposes). A lot are coming out of places where relative cost of compute compared to income, may be too high, alternately there may not have access to accepted payment methods?<p>For the servers coming from the US and developed East Asia it could be already cyber companies doing scanning to find clients, or already compromised servers?
If you're lucky enough to have a big ISP with a single big block of IP addresses that never changes you can disallow all other ranges on your VPS admin ports and only have to worry about VPNing through that ISP.<p>I guess you could block the main country offenders but you'd have to pay an API to keep up with the IP allocations to be sure.
why is ssh open to the internet to begin with?<p>ufw is the first thing I install, even on a "private" network and here's why.<p>I recently installed a router with IPv4 and IPV6. I later found out that IPv6 was globally addressed with no firewall.<p>Always run ufw and begin by shutting off everything to the internet, then only open up what you need.
I automate the hell out of packet capture, using the max ipinfo free tier each month... graph db... I cluster packets, organization dossier, and other collections of data as embeddings. Helps cut noise and identify anomalies faster.
So this made me realise where I could find the SSH log file, and I spent a little while panicking at just how many attempts I've been getting on my webserver, and locking things down just a little harder out of paranoia
I have been doing similar, albeit less complex analysis, of incoming malicious, and it's always surprising the amount of relentless attacks. Any good practices to maintain a secure online server?
> Finding the location of each attacker.<p>...of the attacking IP address, not attacker...<p>If I, living in a small EU country, wanted to "hack" my neighbour across the street, I sure as hell wouldn't use my home IP address, tied to my account at my ISP, which has my name and address.<p>I'd probably try to find an "IP" (VM, vpn, or whatever) in a country that's not really friendly about giving "ip address data" to our authorities.<p>On the other hand, I wouldn't use a chinese IP in china, if I lived there and wanted to hack my neighbour over there.