This IP address has been reported a total of
743
times from
375 distinct
sources.
122.129.80.52 was first reported on
, and the most recent report was
.
Old Reports:
The most recent abuse report for this IP address is from
. It is possible that this IP is no longer involved in abusive activities.
Jun 24 12:14:15 vanillarpbg sshd[123732]: pam_unix(sshd:auth): authentication failure; logname= uid= ...
show moreJun 24 12:14:15 vanillarpbg sshd[123732]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52
Jun 24 12:14:15 vanillarpbg sshd[123732]: Invalid user user from 122.129.80.52 port 43130
Jun 24 12:14:18 vanillarpbg sshd[123732]: Failed password for invalid user user from 122.129.80.52 port 43130 ssh2
Jun 24 12:15:18 vanillarpbg sshd[123896]: Invalid user admin from 122.129.80.52 port 57862
Jun 24 12:15:18 vanillarpbg sshd[123896]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52
Jun 24 12:15:18 vanillarpbg sshd[123896]: Invalid user admin from 122.129.80.52 port 57862
Jun 24 12:15:20 vanillarpbg sshd[123896]: Failed password for invalid user admin from 122.129.80.52 port 57862 ssh2
...
show less
Jun 24 11:20:23 login sshd[6975]: Failed password for root from 122.129.80.52 port 33462 ssh2
Jun 24 ...
show moreJun 24 11:20:23 login sshd[6975]: Failed password for root from 122.129.80.52 port 33462 ssh2
Jun 24 11:21:30 login sshd[7025]: Failed password for root from 122.129.80.52 port 48642 ssh2
...
show less
Jun 24 11:02:45 ns37 sshd[11170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 ...
show moreJun 24 11:02:45 ns37 sshd[11170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52
Jun 24 11:02:47 ns37 sshd[11170]: Failed password for invalid user test from 122.129.80.52 port 33022 ssh2
Jun 24 11:03:52 ns37 sshd[11215]: Failed password for root from 122.129.80.52 port 48132 ssh2
...
show less
Jun 24 08:38:57 cloud sshd[418362]: Invalid user admin from 122.129.80.52 port 58890
Jun 24 08:41:57 ...
show moreJun 24 08:38:57 cloud sshd[418362]: Invalid user admin from 122.129.80.52 port 58890
Jun 24 08:41:57 cloud sshd[418458]: Invalid user userftp from 122.129.80.52 port 38378
...
show less
Jun 24 10:33:48 ns37 sshd[6989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 ...
show moreJun 24 10:33:48 ns37 sshd[6989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52
Jun 24 10:33:50 ns37 sshd[6989]: Failed password for invalid user admin from 122.129.80.52 port 33428 ssh2
Jun 24 10:40:23 ns37 sshd[7829]: Failed password for root from 122.129.80.52 port 54534 ssh2
...
show less
Jun 24 08:33:36 sanyalnet-oracle-vps2 sshd[792894]: pam_unix(sshd:auth): authentication failure; log ...
show moreJun 24 08:33:36 sanyalnet-oracle-vps2 sshd[792894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52
Jun 24 08:33:39 sanyalnet-oracle-vps2 sshd[792894]: Failed password for invalid user admin from 122.129.80.52 port 34378 ssh2
Jun 24 08:33:39 sanyalnet-oracle-vps2 sshd[792894]: Disconnected from invalid user admin 122.129.80.52 port 34378 [preauth]
...
show less
Jun 24 10:02:04 epaper-docker-02 sshd[2326017]: User root from 122.129.80.52 not allowed because non ...
show moreJun 24 10:02:04 epaper-docker-02 sshd[2326017]: User root from 122.129.80.52 not allowed because none of user's groups are listed in AllowGroups
Jun 24 10:02:04 epaper-docker-02 sshd[2326017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52 user=root
Jun 24 10:02:05 epaper-docker-02 sshd[2326017]: Failed password for invalid user root from 122.129.80.52 port 48146 ssh2
Jun 24 10:03:09 epaper-docker-02 sshd[2340281]: Connection from 122.129.80.52 port 34812 on 176.9.120.211 port 22 rdomain ""
Jun 24 10:03:10 epaper-docker-02 sshd[2340281]: User root from 122.129.80.52 not allowed because none of user's groups are listed in AllowGroups
...
show less
Jun 24 03:29:41 vps-6 sshd[2066650]: Failed password for invalid user debian from 122.129.80.52 port ...
show moreJun 24 03:29:41 vps-6 sshd[2066650]: Failed password for invalid user debian from 122.129.80.52 port 46094 ssh2
Jun 24 03:30:40 vps-6 sshd[2066770]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52 user=root
Jun 24 03:30:42 vps-6 sshd[2066770]: Failed password for root from 122.129.80.52 port 33116 ssh2
...
show less
Jun 24 03:12:29 vps-6 sshd[2065396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eui ...
show moreJun 24 03:12:29 vps-6 sshd[2065396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52 user=root
Jun 24 03:12:31 vps-6 sshd[2065396]: Failed password for root from 122.129.80.52 port 55920 ssh2
Jun 24 03:13:38 vps-6 sshd[2065496]: Invalid user test from 122.129.80.52 port 42966
...
show less
Brute-Force
SSH
Anonymous
2024-06-24T09:04:46.410925+02:00 svr10 sshd[1043224]: Disconnected from authenticating user root 122 ...
show more2024-06-24T09:04:46.410925+02:00 svr10 sshd[1043224]: Disconnected from authenticating user root 122.129.80.52 port 39986 [preauth]
2024-06-24T09:12:06.555063+02:00 svr10 sshd[1045653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52 user=root
2024-06-24T09:12:08.784208+02:00 svr10 sshd[1045653]: Failed password for root from 122.129.80.52 port 36930 ssh2
...
show less
Jun 24 07:13:13 lms sshd[32221]: Failed password for root from 122.129.80.52 port 54272 ssh2
Jun 24 ...
show moreJun 24 07:13:13 lms sshd[32221]: Failed password for root from 122.129.80.52 port 54272 ssh2
Jun 24 07:18:02 lms sshd[32555]: Failed password for root from 122.129.80.52 port 38562 ssh2
Jun 24 07:19:14 lms sshd[32691]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.129.80.52
...
show less
Brute-Force
SSH
Showing 1 to
15
of 743 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩