AbuseIPDB » 20.83.161.155

20.83.161.155 was found in our database!

This IP was reported 29 times. Confidence of Abuse is 67%: ?

67%

ISP	Microsoft Corporation
Usage Type	Data Center/Web Hosting/Transit
ASN	AS8075
Domain Name	microsoft.com
Country	United States of America
City	Washington, Virginia

IP info including ISP, Usage Type, and Location provided by IPInfo. Updated biweekly.

Report 20.83.161.155

Whois 20.83.161.155

IP Abuse Reports for 20.83.161.155:

This IP address has been reported a total of 29 times from 16 distinct sources. 20.83.161.155 was first reported on June 10th 2025, and the most recent report was 1 week ago.

Old Reports: The most recent abuse report for this IP address is from 1 week ago. It is possible that this IP is no longer involved in abusive activities.

Reporter	IoA Timestamp in UTC	Comment	Categories
rtbh.com.tr	2025-06-12 20:07:06 (1 week ago)	list.rtbh.com.tr report: tcp/0	Brute-Force
rtbh.com.tr	2025-06-11 20:07:05 (1 week ago)	list.rtbh.com.tr report: tcp/0	Brute-Force
Anonymous	2025-06-10 18:49:49 (1 week ago)	Jun 10 18:49:46 ubuntu sshd[10906]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid ... show moreJun 10 18:49:46 ubuntu sshd[10906]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.83.161.155 Jun 10 18:49:48 ubuntu sshd[10906]: Failed password for invalid user tejas from 20.83.161.155 port 43358 ssh2 Jun 10 18:49:46 ubuntu sshd[10906]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.83.161.155 Jun 10 18:49:48 ubuntu sshd[10906]: Failed password for invalid user tejas from 20.83.161.155 port 43358 ssh2 Jun 10 18:49:49 ubuntu sshd[10906]: Disconnected from invalid user tejas 20.83.161.155 port 43358 [preauth] ... show less	Brute-Force SSH
linuxgemini	2025-06-10 17:55:08 (1 week ago)	fail2banned (ssh brute)	Brute-Force SSH
diego	2025-06-10 17:52:46 (1 week ago)	[rede-44-49] (sshd) Failed SSH login from 20.83.161.155 (US/United States/-): 5 in the last 3600 sec ... show more[rede-44-49] (sshd) Failed SSH login from 20.83.161.155 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Jun 10 14:39:44 sshd[17518]: Invalid user [USERNAME] from 20.83.161.155 port 32900 Jun 10 14:39:46 sshd[17518]: Failed password for invalid user [USERNAME] from 20.83.161.155 port 32900 ssh2 Jun 10 14:48:32 sshd[18109]: Invalid user [USERNAME] from 20.83.161.155 port 60830 Jun 10 14:48:34 sshd[18109]: Failed password for invalid user [USERNAME] from 20.83.161.155 port 60830 ssh2 Jun 10 14:52:43 sshd[18377]: Invalid user [USERNAME] from 20.83.161.155 port 51558 show less	Port Scan
Jake___	2025-06-10 17:52:28 (1 week ago)	Unauthorized access via ssh 20.83.161.155	Brute-Force SSH
Anonymous	2025-06-10 17:46:50 (1 week ago)	Jun 10 17:34:30 ubuntu sshd[10737]: Failed password for invalid user vtatis from 20.83.161.155 port ... show moreJun 10 17:34:30 ubuntu sshd[10737]: Failed password for invalid user vtatis from 20.83.161.155 port 34566 ssh2 Jun 10 17:34:32 ubuntu sshd[10737]: Disconnected from invalid user vtatis 20.83.161.155 port 34566 [preauth] Jun 10 17:46:48 ubuntu sshd[10749]: Invalid user deepak from 20.83.161.155 port 41876 Jun 10 17:46:48 ubuntu sshd[10749]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.83.161.155 Jun 10 17:46:50 ubuntu sshd[10749]: Failed password for invalid user deepak from 20.83.161.155 port 41876 ssh2 ... show less	Brute-Force SSH
hanb.jp	2025-06-10 17:39:10 (1 week ago)	Jun 10 17:38:14 v4bgp sshd[3958491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eui ... show moreJun 10 17:38:14 v4bgp sshd[3958491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.83.161.155 Jun 10 17:38:16 v4bgp sshd[3958491]: Failed password for invalid user vtatis from 20.83.161.155 port 36520 ssh2 Jun 10 17:39:09 v4bgp sshd[3958536]: Invalid user vtatis from 20.83.161.155 port 53126 ... show less	Brute-Force SSH
Study Bitcoin 🤗	2025-06-10 17:24:29 (1 week ago)	4 port probes: 4x tcp/22 (ssh) [srv129]	Port Scan Brute-Force SSH
Study Bitcoin 🤗	2025-06-10 17:06:26 (1 week ago)	4 port probes: 4x tcp/22 (ssh) [srv129]	Port Scan Brute-Force SSH
Study Bitcoin 🤗	2025-06-10 16:52:27 (1 week ago)	3 port probes: 3x tcp/22 (ssh) [srv129]	Port Scan Brute-Force SSH
PieKnu	2025-06-10 16:40:34 (1 week ago)	Jun 10 16:31:43 host sshd[1284218]: Failed password for invalid user netbox from 20.83.161.155 port ... show moreJun 10 16:31:43 host sshd[1284218]: Failed password for invalid user netbox from 20.83.161.155 port 36490 ssh2 Jun 10 16:36:06 host sshd[1287673]: Invalid user mgeweb from 20.83.161.155 port 46300 Jun 10 16:36:06 host sshd[1287673]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.83.161.155 Jun 10 16:36:08 host sshd[1287673]: Failed password for invalid user mgeweb from 20.83.161.155 port 46300 ssh2 Jun 10 16:40:34 host sshd[1291163]: Invalid user me from 20.83.161.155 port 57198 ... show less	Brute-Force SSH
Study Bitcoin 🤗	2025-06-10 16:40:23 (1 week ago)	3 port probes: 3x tcp/22 (ssh) [srv129]	Port Scan Brute-Force SSH
trivox.sh	2025-06-10 16:34:14 (1 week ago)	Jun 10 16:29:39 honey3 sshd[1742601]: Failed password for invalid user openeuler from 20.83.161.155 ... show moreJun 10 16:29:39 honey3 sshd[1742601]: Failed password for invalid user openeuler from 20.83.161.155 port 33150 ssh2 Jun 10 16:29:39 honey3 sshd[1742601]: Disconnected from invalid user openeuler 20.83.161.155 port 33150 [preauth] Jun 10 16:34:12 honey3 sshd[1742966]: Invalid user netbox from 20.83.161.155 port 57434 Jun 10 16:34:12 honey3 sshd[1742966]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=20.83.161.155 Jun 10 16:34:13 honey3 sshd[1742966]: Failed password for invalid user netbox from 20.83.161.155 port 57434 ssh2 ... show less	Brute-Force SSH
Study Bitcoin 🤗	2025-06-10 16:22:22 (1 week ago)	4 port probes: 4x tcp/22 (ssh) [srv129]	Port Scan Brute-Force SSH

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