AbuseIPDB » 139.59.102.10

139.59.102.10 was found in our database!

This IP was reported 4,492 times. Confidence of Abuse is 100%: ?

100%

ISP	DigitalOcean LLC
Usage Type	Data Center/Web Hosting/Transit
Hostname(s)	epost.com.bd
Domain Name	digitalocean.com
Country	Singapore
City	Singapore, Singapore

IP info including ISP, Usage Type, and Location provided by IP2Location. Updated monthly.

Report 139.59.102.10

Whois 139.59.102.10

IP Abuse Reports for 139.59.102.10:

This IP address has been reported a total of 4,492 times from 790 distinct sources. 139.59.102.10 was first reported on June 13th 2022, and the most recent report was 4 hours ago.

Recent Reports: We have received reports of abusive activity from this IP address within the last week. It is potentially still actively engaged in abusive activities.

Reporter	Date	Comment	Categories
hackersare.us	4 hours ago	Jan 29 03:08:10 dotcom2 sshd\[7545\]: User root from 139.59.102.10 not allowed because not listed in ... show moreJan 29 03:08:10 dotcom2 sshd\[7545\]: User root from 139.59.102.10 not allowed because not listed in AllowUsers Jan 29 03:08:10 dotcom2 sshd\[7545\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root ... show less	Brute-Force SSH
A	5 hours ago	Jan 29 07:57:48 xxx sshd[1141439]: Invalid user root from 139.59.102.10 port 42830 ssh2 Jan 29 ... show moreJan 29 07:57:48 xxx sshd[1141439]: Invalid user root from 139.59.102.10 port 42830 ssh2 Jan 29 08:00:43 xxx sshd[1216478]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 29 08:00:45 xxx sshd[1216478]: Invalid user root from 139.59.102.10 port 49166 ssh2 Jan 29 08:02:45 xxx sshd[1264610]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 29 08:02:47 xxx sshd[1264610]: Invalid user root from 139.59.102.10 port 49796 ssh2 ... show less	Brute-Force SSH
Anonymous	7 hours ago	Jan 29 04:22:58 f2b auth.info sshd[44778]: Failed password for root from 139.59.102.10 port 34396 ss ... show moreJan 29 04:22:58 f2b auth.info sshd[44778]: Failed password for root from 139.59.102.10 port 34396 ssh2 Jan 29 04:25:53 f2b auth.info sshd[44806]: Failed password for root from 139.59.102.10 port 41444 ssh2 Jan 29 04:28:00 f2b auth.info sshd[44820]: Failed password for root from 139.59.102.10 port 44622 ssh2 ... show less	Brute-Force SSH
filip2cz	7 hours ago	Jan 29 05:25:49 status sshd[3627573]: Failed password for root from 139.59.102.10 port 58394 ssh2<br ... show moreJan 29 05:25:49 status sshd[3627573]: Failed password for root from 139.59.102.10 port 58394 ssh2 Jan 29 05:27:53 status sshd[3630235]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 29 05:27:56 status sshd[3630235]: Failed password for root from 139.59.102.10 port 33340 ssh2 ... show less	Brute-Force SSH
LRNP	12 hours ago	Jan 28 23:32:20 helium sshd[1252863]: Disconnected from authenticating user root 139.59.102.10 port ... show moreJan 28 23:32:20 helium sshd[1252863]: Disconnected from authenticating user root 139.59.102.10 port 46758 [preauth] Jan 28 23:37:18 helium sshd[1252918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 23:37:20 helium sshd[1252918]: Failed password for root from 139.59.102.10 port 41014 ssh2 ... show less	Brute-Force SSH
LoNET	14 hours ago	Report 62667 with IP 787305 for SSH brute-force attack by source 1104890 via ssh-honeypot/0.2.0+http	Brute-Force SSH
0attack.com	15 hours ago	SSH login attempts	Brute-Force SSH
gen_angry	15 hours ago	Jan 28 21:15:19 vps-714b20ba sshd[5770]: Failed password for root from 139.59.102.10 port 46934 ssh2 ... show moreJan 28 21:15:19 vps-714b20ba sshd[5770]: Failed password for root from 139.59.102.10 port 46934 ssh2 Jan 28 21:17:51 vps-714b20ba sshd[5779]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 21:17:53 vps-714b20ba sshd[5779]: Failed password for root from 139.59.102.10 port 54034 ssh2 ... show less	Brute-Force SSH
gen_angry	16 hours ago	Jan 28 20:09:45 vps-714b20ba sshd[5301]: Failed password for root from 139.59.102.10 port 52874 ssh2 ... show moreJan 28 20:09:45 vps-714b20ba sshd[5301]: Failed password for root from 139.59.102.10 port 52874 ssh2 Jan 28 20:11:40 vps-714b20ba sshd[5354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 20:11:42 vps-714b20ba sshd[5354]: Failed password for root from 139.59.102.10 port 59972 ssh2 ... show less	Brute-Force SSH
Huettersen	16 hours ago	2023-01-28T20:05:11.162021Z 08d7b70f1994 New connection: 139.59.102.10:39172 (172.16.16.215:2222) [s ... show more2023-01-28T20:05:11.162021Z 08d7b70f1994 New connection: 139.59.102.10:39172 (172.16.16.215:2222) [session: 08d7b70f1994] 2023-01-28T20:09:11.795871Z 80f9815f32b6 New connection: 139.59.102.10:60316 (172.16.16.215:2222) [session: 80f9815f32b6] show less	Brute-Force SSH
Anonymous	18 hours ago	Jan 28 18:17:17 hosting06 sshd[2280155]: Failed password for root from 139.59.102.10 port 55926 ssh2 ... show moreJan 28 18:17:17 hosting06 sshd[2280155]: Failed password for root from 139.59.102.10 port 55926 ssh2 Jan 28 18:22:59 hosting06 sshd[2281814]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 18:23:01 hosting06 sshd[2281814]: Failed password for root from 139.59.102.10 port 50034 ssh2 Jan 28 18:24:51 hosting06 sshd[2282428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 18:24:53 hosting06 sshd[2282428]: Failed password for root from 139.59.102.10 port 52210 ssh2 ... show less	Brute-Force SSH
MU-star.net	21 hours ago	Invalid user linaro from 139.59.102.10 port 60570	Port Scan Brute-Force SSH
Christopher Hughes	22 hours ago	Jan 28 13:52:32 Ubuntu-2204-jammy-amd64-base sshd[2913898]: Failed password for root from 139.59.102 ... show moreJan 28 13:52:32 Ubuntu-2204-jammy-amd64-base sshd[2913898]: Failed password for root from 139.59.102.10 port 56944 ssh2 Jan 28 13:54:30 Ubuntu-2204-jammy-amd64-base sshd[2914013]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 13:54:33 Ubuntu-2204-jammy-amd64-base sshd[2914013]: Failed password for root from 139.59.102.10 port 36270 ssh2 Jan 28 13:56:31 Ubuntu-2204-jammy-amd64-base sshd[2914077]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 13:56:33 Ubuntu-2204-jammy-amd64-base sshd[2914077]: Failed password for root from 139.59.102.10 port 43828 ssh2 ... show less	Brute-Force SSH
OHOST.BG	22 hours ago	2023-01-28T15:52:24.768132anubis.d-serv.eu sshd[4740]: Failed password for root from 139.59.102.10 p ... show more2023-01-28T15:52:24.768132anubis.d-serv.eu sshd[4740]: Failed password for root from 139.59.102.10 port 57396 ssh2 2023-01-28T15:54:23.140025anubis.d-serv.eu sshd[1495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root 2023-01-28T15:54:25.564754anubis.d-serv.eu sshd[1495]: Failed password for root from 139.59.102.10 port 36722 ssh2 2023-01-28T15:56:23.562927anubis.d-serv.eu sshd[48232]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root 2023-01-28T15:56:26.127718anubis.d-serv.eu sshd[48232]: Failed password for root from 139.59.102.10 port 44278 ssh2 ... show less	Brute-Force SSH
miklos_akos	22 hours ago	Jan 28 14:51:27 nsmailweb sshd[678693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 ... show moreJan 28 14:51:27 nsmailweb sshd[678693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.102.10 user=root Jan 28 14:51:30 nsmailweb sshd[678693]: Failed password for root from 139.59.102.10 port 47886 ssh2 ... show less	Brute-Force SSH

Is this your IP? You may request to takedown any associated reports. We will attempt to verify your ownership. Request Takedown 🚩