Go
139.59.141.137
is a
Hacker
100 %
Germany
Report Abuse
1019attacks reported
821Brute-ForceSSH
84Brute-Force
48SSH
20Port ScanBrute-ForceSSH
9HackingBrute-ForceSSH
9uncategorized
6DDoS Attack
5Port ScanSSH
4Port ScanHackingBrute-ForceWeb App AttackSSH
3Hacking
...
from 153 distinct reporters
and 8 distinct sources : BadIPs.com, Blocklist.de, darklist.de, FireHOL, Charles Haley, NoThink.org, NormShield.com, AbuseIPDB
139.59.141.137 was first signaled at 2018-09-16 09:23 and last record was at 2019-07-21 21:19.
IP

139.59.141.137

Organization
DigitalOcean, LLC
Localisation
Germany
Hessen, Frankfurt
NetRange : First & Last IP
139.59.0.0 - 139.59.255.254
Network CIDR
139.59.0.0/16

Cybercrime IP Feeds

Date UTC Category Sub Categories Source List Source Logs
2019-04-04 22:46 attacks Brute-Force AbuseIPDB Apr 5 07:46:09 marvibiene sshd[27297]: Invalid user hanoop from 139.59.141.137 port 39454 Apr 5 07:46:09 marvibiene sshd[27297]: pam_unix(sshd:auth):
2019-04-04 16:06 attacks Port Scan AbuseIPDB Scanning for vulnerable services
2019-04-04 15:39 attacks Brute-ForceSSH AbuseIPDB Apr 5 02:39:26 ubuntu-2gb-nbg1-dc3-1 sshd[29540]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.1
2019-04-04 15:02 attacks Brute-ForceSSH AbuseIPDB Apr 4 23:59:02 *** sshd[19041]: Invalid user tomcat from 139.59.141.137
2019-04-04 13:27 attacks Brute-ForceSSH AbuseIPDB Apr 4 22:26:57 MK-Soft-VM4 sshd\[2014\]: Invalid user ts3ovh from 139.59.141.137 port 48324 Apr 4 22:26:57 MK-Soft-VM4 sshd\[2014\]: pam_unix\(sshd:au
2019-04-04 12:57 attacks Brute-Force AbuseIPDB Apr 4 21:57:23 work-partkepr sshd\[19450\]: User list from 139.59.141.137 not allowed because not listed in AllowUsers Apr 4 21:57:23 work-partkepr ss
2019-04-04 10:23 attacks Brute-ForceSSH AbuseIPDB SSH Bruteforce Attack
2019-04-04 10:06 attacks Brute-ForceSSH AbuseIPDB Apr 4 21:06:12 [host] sshd[25872]: Invalid user amanda from 139.59.141.137 Apr 4 21:06:12 [host] sshd[25872]: pam_unix(sshd:auth): authentication fail
2019-04-04 09:51 attacks Brute-ForceSSH AbuseIPDB Apr 4 06:12:04 Ubuntu-1404-trusty-64-minimal sshd\[19535\]: Invalid user stephen from 139.59.141.137 Apr 4 06:12:04 Ubuntu-1404-trusty-64-minimal sshd
2019-04-04 09:02 attacks Brute-Force AbuseIPDB Apr 4 20:00:43 herz-der-gamer sshd[1815]: Invalid user anonimus from 139.59.141.137 port 34478 Apr 4 20:00:43 herz-der-gamer sshd[1815]: pam_unix(sshd
2019-04-04 09:02 attacks DDoS AttackSSH AbuseIPDB Apr 4 19:00:56 l02a sshd\[3921\]: Invalid user anonimus from 139.59.141.137 Apr 4 19:00:56 l02a sshd\[3921\]: pam_unix\(sshd:auth\): authentication fa
2019-04-04 08:04 attacks Brute-ForceSSH AbuseIPDB Apr 4 19:04:05 MK-Soft-Root2 sshd\[28936\]: Invalid user postmaster from 139.59.141.137 port 55470 Apr 4 19:04:05 MK-Soft-Root2 sshd\[28936\]: pam_uni
2019-04-03 18:04 attacks Brute-ForceSSH AbuseIPDB Apr 4 05:04:00 ubuntu-2gb-nbg1-dc3-1 sshd[29027]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.1
2019-04-03 17:34 attacks Brute-ForceSSH AbuseIPDB Apr 3 22:34:35 debian sshd\[19758\]: Invalid user ftp1 from 139.59.141.137 port 45172 Apr 3 22:34:35 debian sshd\[19758\]: pam_unix\(sshd:auth\): auth
2019-04-03 12:53 attacks Port ScanBrute-ForceSSH AbuseIPDB $f2bV_matches
2019-04-03 10:37 attacks Brute-ForceSSH AbuseIPDB Apr 3 21:37:50 v22018076622670303 sshd\[22598\]: Invalid user PlcmSpIp from 139.59.141.137 port 56918 Apr 3 21:37:50 v22018076622670303 sshd\[22598\]:
2019-04-03 10:17 attacks Brute-ForceSSH AbuseIPDB Apr 3 21:10:48 core01 sshd\[17818\]: Invalid user oi from 139.59.141.137 port 45436 Apr 3 21:10:48 core01 sshd\[17818\]: pam_unix\(sshd:auth\): authen
2019-04-03 08:47 attacks Brute-ForceSSH AbuseIPDB Apr 3 19:47:39 bouncer sshd\[24163\]: Invalid user www from 139.59.141.137 port 52650 Apr 3 19:47:39 bouncer sshd\[24163\]: pam_unix\(sshd:auth\): aut
2019-04-03 07:35 attacks Brute-ForceSSH AbuseIPDB Apr 3 18:35:28 PowerEdge sshd\[26260\]: Invalid user castis from 139.59.141.137 Apr 3 18:35:28 PowerEdge sshd\[26260\]: pam_unix\(sshd:auth\): authent
2019-04-03 07:24 attacks Brute-ForceSSH AbuseIPDB  
2019-04-03 05:21 attacks Brute-ForceSSH AbuseIPDB Apr 3 15:15:40 marquez sshd[613]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.137 Apr 3 15:15:4
2019-04-03 04:40 attacks Brute-ForceSSH AbuseIPDB Apr 3 15:34:22 core01 sshd\[12420\]: Invalid user test from 139.59.141.137 port 59236 Apr 3 15:34:22 core01 sshd\[12420\]: pam_unix\(sshd:auth\): auth
2019-04-03 03:33 attacks Brute-ForceSSH AbuseIPDB 2019-04-03T14:33:25.158734centos sshd\[24421\]: Invalid user wp-user from 139.59.141.137 port 45578 2019-04-03T14:33:25.163571centos sshd\[24421\]: pa
2019-04-03 02:04 attacks Brute-ForceSSH AbuseIPDB Apr 3 12:59:34 cp sshd[3053]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.137 Apr 3 12:59:35 cp
2019-04-02 12:48 attacks Brute-ForceSSH AbuseIPDB Apr 2 23:48:14 [host] sshd[10769]: Invalid user nodeserver from 139.59.141.137 Apr 2 23:48:14 [host] sshd[10769]: pam_unix(sshd:auth): authentication
2019-04-02 11:07 attacks Brute-ForceSSH AbuseIPDB SSH Bruteforce Attack
2019-04-02 10:34 attacks Brute-ForceSSH AbuseIPDB Apr 2 21:29:29 vserver sshd\[15150\]: Invalid user MayGion from 139.59.141.137Apr 2 21:29:31 vserver sshd\[15150\]: Failed password for invalid user M
2019-04-02 10:09 attacks Brute-ForceSSH AbuseIPDB Apr 2 21:09:21 vps65 sshd\[27848\]: Invalid user g from 139.59.141.137 port 56328 Apr 2 21:09:21 vps65 sshd\[27848\]: pam_unix\(sshd:auth\): authentic
2019-04-02 08:31 attacks SSH AbuseIPDB ssh-bruteforce
2019-04-02 08:06 attacks Brute-ForceSSH AbuseIPDB Apr 2 17:05:57 *** sshd[2987]: Invalid user usuario from 139.59.141.137
2019-04-02 06:43 attacks Brute-ForceSSH AbuseIPDB Apr 2 17:37:36 dev0-dcde-rnet sshd[24589]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.137 Apr
2019-04-02 03:19 attacks Brute-ForceSSH AbuseIPDB Apr 2 14:19:08 mail sshd\[15407\]: Invalid user test from 139.59.141.137 port 47480 Apr 2 14:19:08 mail sshd\[15407\]: Disconnected from 139.59.141.13
2019-04-02 00:03 attacks Brute-Force AbuseIPDB DATE:2019-04-02 11:03:15,IP:139.59.141.137,MATCHES:2,PORT:22 Brute force on a honeypot SSH server
2019-04-01 22:13 attacks Brute-ForceSSH AbuseIPDB SSH Brute-Force reported by Fail2Ban
2019-04-01 20:39 attacks Brute-ForceSSH AbuseIPDB F2B jail: sshd. Time: 2019-04-02 07:39:27, Reported by: VKReport
2019-04-01 20:35 attacks Brute-ForceSSH AbuseIPDB Apr 2 07:34:56 srv206 sshd[28683]: Invalid user ht from 139.59.141.137 Apr 2 07:34:56 srv206 sshd[28683]: pam_unix(sshd:auth): authentication failure;
2019-04-01 18:01 attacks Brute-ForceSSH AbuseIPDB  
2019-04-01 16:53 attacks Brute-ForceSSH AbuseIPDB Apr 1 21:49:08 localhost sshd[12347]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.137 Apr 1 21:
2019-04-01 15:58 attacks Brute-ForceSSH AbuseIPDB Apr 2 02:58:26 nextcloud sshd\[27244\]: Invalid user vagrant from 139.59.141.137 Apr 2 02:58:26 nextcloud sshd\[27244\]: pam_unix\(sshd:auth\): authen
2019-04-01 14:53 attacks Brute-ForceSSH AbuseIPDB Apr 2 01:53:47 vmd17057 sshd\[4249\]: Invalid user system from 139.59.141.137 port 46924 Apr 2 01:53:47 vmd17057 sshd\[4249\]: pam_unix\(sshd:auth\):
2019-04-01 14:20 attacks Brute-ForceSSH AbuseIPDB ssh failed login
2019-04-01 14:16 attacks Brute-ForceSSH AbuseIPDB Tried sshing with brute force.
2019-04-01 13:06 attacks Brute-ForceSSH AbuseIPDB Apr 2 00:06:32 mail sshd[3780]: Invalid user ia from 139.59.141.137
2019-04-01 12:23 attacks Brute-ForceSSH AbuseIPDB Apr 1 21:23:15 MK-Soft-VM3 sshd\[31080\]: Invalid user ubuntu from 139.59.141.137 port 58004 Apr 1 21:23:15 MK-Soft-VM3 sshd\[31080\]: pam_unix\(sshd:
2019-04-01 11:05 attacks Brute-ForceSSH AbuseIPDB Apr 1 08:49:28 *** sshd[12462]: Failed password for invalid user shop1 from 139.59.141.137 port 43878 ssh2 Apr 1 08:52:37 *** sshd[12501]: Failed pass
2019-04-01 04:11 attacks Brute-ForceSSH AbuseIPDB Apr 1 09:05:43 plusreed sshd[22437]: Invalid user git3 from 139.59.141.137 Apr 1 09:05:43 plusreed sshd[22437]: pam_unix(sshd:auth): authentication fa
2019-04-01 03:35 attacks Brute-ForceSSH AbuseIPDB Apr 1 14:31:01 meumeu sshd[4045]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.137 Apr 1 14:31:
2019-04-01 01:10 attacks Brute-ForceSSH AbuseIPDB Apr 1 12:10:49 ubuntu-2gb-nbg1-dc3-1 sshd[14803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.1
2019-03-31 20:32 attacks Port ScanBrute-ForceSSH AbuseIPDB Apr 1 07:26:50 MainVPS sshd[21806]: Invalid user vy from 139.59.141.137 port 47292 Apr 1 07:26:50 MainVPS sshd[21806]: pam_unix(sshd:auth): authentica
2019-03-31 16:56 attacks Brute-ForceSSH AbuseIPDB SSH-Bruteforce
2018-09-16 09:23 attacks FTP Brute-ForceHacking AbuseIPDB Sep 16 20:18:55 *** sshd[27166]: Address 139.59.141.137 maps to prospectos-ubuntu-16.04, but this does not map back to the address - POSSIBLE BREAK-IN
2018-09-25 20:35 attacks Brute-ForceSSH AbuseIPDB SSH Bruteforce @ SigaVPN honeypot
2018-09-30 10:25 attacks Brute-ForceSSH AbuseIPDB Several tries of breaking-in -ms556.moonshot.servdiscount-customer.com
2018-10-01 01:04 attacks SSH AbuseIPDB ssh bruteforce J
2018-10-01 01:11 attacks Brute-Force AbuseIPDB $f2bV_matches
2018-10-01 09:10 attacks Brute-ForceSSH AbuseIPDB Oct 1 11:10:41 cac1d2 sshd\[22003\]: Invalid user admin from 139.59.141.137 port 54168 Oct 1 11:10:41 cac1d2 sshd\[22003\]: pam_unix\(sshd:auth\): aut
2018-10-01 12:42 attacks Brute-ForceSSH AbuseIPDB Oct 1 16:00:58 localhost sshd[28802]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.141.137 Oct 1 16:
2018-10-04 09:03 attacks Brute-ForceSSH AbuseIPDB Oct 4 21:03:31 srv-4 sshd\[20310\]: Invalid user csgoserver from 139.59.141.137 Oct 4 21:03:31 srv-4 sshd\[20310\]: pam_unix\(sshd:auth\): authenticat
2018-10-04 10:42 attacks Brute-ForceSSH AbuseIPDB Oct 4 22:41:56 srv-4 sshd\[9668\]: Invalid user admin from 139.59.141.137 Oct 4 22:41:56 srv-4 sshd\[9668\]: pam_unix\(sshd:auth\): authentication fai
2018-10-04 12:21 attacks Brute-ForceSSH AbuseIPDB Oct 5 00:21:54 srv-4 sshd\[2784\]: Invalid user infra from 139.59.141.137 Oct 5 00:21:54 srv-4 sshd\[2784\]: pam_unix\(sshd:auth\): authentication fai
2019-03-29 18:18 attacks bi_any_0_1d BadIPs.com  
2019-03-29 18:19 attacks Bad Web Bot bi_badbots_0_1d BadIPs.com  
2019-03-29 18:19 attacks Brute-Force bi_bruteforce_0_1d BadIPs.com  
2019-03-29 18:20 attacks SSH bi_sshd_0_1d BadIPs.com  
2019-03-29 18:20 attacks SSH bi_ssh_0_1d BadIPs.com  
2019-03-29 18:21 attacks blocklist_de Blocklist.de  
2019-03-29 18:21 attacks SSH blocklist_de_ssh Blocklist.de  
2019-03-29 18:23 attacks darklist_de darklist.de  
2019-03-29 18:27 attacks firehol_level2 FireHOL  
2019-03-29 18:28 attacks firehol_level4 FireHOL  
2019-03-29 18:34 attacks SSH haley_ssh Charles Haley  
2019-05-28 23:20 attacks blocklist_de_strongips Blocklist.de  
2019-06-03 23:00 attacks SSH nt_ssh_7d NoThink.org  
2019-06-21 05:52 attacks bi_default_0_1d BadIPs.com  
2019-06-21 05:53 attacks bi_unknown_0_1d BadIPs.com  
2019-07-05 14:44 attacks Brute-Force normshield_all_bruteforce NormShield.com  
2019-07-05 14:44 attacks Brute-Force normshield_high_bruteforce NormShield.com  
2019-07-21 21:19 attacks Fraud VoIP blocklist_de_sip Blocklist.de  
2019-03-29 18:34 attacks firehol_webserver FireHOL  
only last 50 and first 10 AbuseIPDB logs are shown

Threats Categories :

abuse
IPs used to spam forum, boards, blogs or smtp servers, automated web scripts or scrappers (bad bots)
anonymizer
Onion Router IP addresses. TOR network IPs, TOR exit points, socks or ssl proxy.
attacks
bruteforce ssh/ftp/system account, IPs that have been detected by fail2ban, ports scan, vulnerabilities scan, DDoS.
malware
Addresses that have been identified distributing malware, form-grabber and stealer, Viruses, Worms, Trojans, Ransomware, Adware, Spyware

Whois

whois.apnic.net.



inetnum: 139.59.0.0 - 139.59.255.254
netname: DIGITALOCEAN-AP
descr: DigitalOcean, LLC
country: SG
admin-c: DOIA2-AP
tech-c: DOIA2-AP
status: ALLOCATED NON-PORTABLE
mnt-by: MAINT-DIGITALOCEAN-AP
mnt-irt: IRT-DIGITALOCEAN-AP
last-modified: 2017-04-11T13:47:40Z
source: APNIC

irt: IRT-DIGITALOCEAN-AP
address: 101 Avenue of the Americas, 10th Floor, New York NY 10013
e-mail: abuse@digitalocean.com
abuse-mailbox: abuse@digitalocean.com
admin-c: DOIA2-AP
tech-c: DOIA2-AP
auth: # Filtered
mnt-by: MAINT-DIGITALOCEAN-AP
last-modified: 2015-04-02T20:25:58Z
source: APNIC

role: Digital Ocean Inc administrator
address: 101 Avenue of th Americas, 10th Floor, New York NY 10013
country: US
phone: +1 646 397 8051
fax-no: +1 646 397 8051
e-mail: abuse@digitalocean.com
admin-c: DOIA2-AP
tech-c: DOIA2-AP
nic-hdl: DOIA2-AP
mnt-by: MAINT-DIGITALOCEAN-AP
last-modified: 2015-04-02T20:27:52Z
source: APNIC
most specific ip range is highlighted
Updated : 2019-07-03