This IP address has been reported a total of
99
times from
60 distinct
sources.
134.122.62.202 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.
2026-03-01T19:00:23.611475shield sshd\[2491\]: Invalid user postgres from 134.122.62.202 port 39156
...
show more2026-03-01T19:00:23.611475shield sshd\[2491\]: Invalid user postgres from 134.122.62.202 port 39156
2026-03-01T19:00:24.313986shield sshd\[2491\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.62.202
2026-03-01T19:00:26.790238shield sshd\[2491\]: Failed password for invalid user postgres from 134.122.62.202 port 39156 ssh2
2026-03-01T19:01:00.201061shield sshd\[2841\]: Invalid user postgres from 134.122.62.202 port 60546
2026-03-01T19:01:01.160853shield sshd\[2841\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.62.202
show less
2026-03-01T18:57:12.708423+00:00 de-milk-fsn01-100 sshd[1615980]: Invalid user weblogic from 134.122 ...
show more2026-03-01T18:57:12.708423+00:00 de-milk-fsn01-100 sshd[1615980]: Invalid user weblogic from 134.122.62.202 port 59724
2026-03-01T18:57:47.912569+00:00 de-milk-fsn01-100 sshd[1616340]: Invalid user mysql from 134.122.62.202 port 52902
2026-03-01T18:58:23.089830+00:00 de-milk-fsn01-100 sshd[1616768]: Invalid user apache from 134.122.62.202 port 47810
2026-03-01T18:58:58.714021+00:00 de-milk-fsn01-100 sshd[1617137]: Invalid user postgres from 134.122.62.202 port 54986
2026-03-01T18:59:34.115994+00:00 de-milk-fsn01-100 sshd[1617573]: Invalid user postgres from 134.122.62.202 port 59034
...
show less
2026-03-01T18:49:37.497599shield sshd\[1088\]: Invalid user uftp from 134.122.62.202 port 42150
2026 ...
show more2026-03-01T18:49:37.497599shield sshd\[1088\]: Invalid user uftp from 134.122.62.202 port 42150
2026-03-01T18:49:38.067586shield sshd\[1088\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.62.202
2026-03-01T18:49:39.861814shield sshd\[1088\]: Failed password for invalid user uftp from 134.122.62.202 port 42150 ssh2
2026-03-01T18:50:15.126221shield sshd\[1157\]: Invalid user testuser from 134.122.62.202 port 39054
2026-03-01T18:50:15.622214shield sshd\[1157\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.62.202
show less
Honeypot hit: Brute-force attack detected on 22/SSH
• Credentials: test1:test1, test2:test2, test3:t ...
show moreHoneypot hit: Brute-force attack detected on 22/SSH
• Credentials: test1:test1, test2:test2, test3:test3, root:root123, root:root321, root:123, root:321, root:pass, root:qwerty, root:password, root:111111, postgres:postgres, oracle:oracle, user:user
• Number of login attempts: 14
• 12 command(s) were executed during the session
• Client: SSH-2.0-Go
Reported by: https://github.com/sefinek/T-Pot-To-AbuseIPDB
show less
Brute-Force
SSH
Hacking
Anonymous
2026-03-01T19:39:21.266691+01:00 mandelbrot sshd-session[224165]: Invalid user test1 from 134.122.62 ...
show more2026-03-01T19:39:21.266691+01:00 mandelbrot sshd-session[224165]: Invalid user test1 from 134.122.62.202 port 49474
2026-03-01T19:40:05.513539+01:00 mandelbrot sshd-session[225469]: Invalid user test2 from 134.122.62.202 port 36244
2026-03-01T19:40:48.097246+01:00 mandelbrot sshd-session[225880]: Invalid user test3 from 134.122.62.202 port 37106
2026-03-01T19:47:11.601045+01:00 mandelbrot sshd-session[228157]: Invalid user oracle from 134.122.62.202 port 35072
2026-03-01T19:47:47.447282+01:00 mandelbrot sshd-session[228218]: Invalid user user from 134.122.62.202 port 50974
...
show less
2026-03-01T19:39:13.685398+01:00 pingussy sshd-session[3087054]: Invalid user test1 from 134.122.62. ...
show more2026-03-01T19:39:13.685398+01:00 pingussy sshd-session[3087054]: Invalid user test1 from 134.122.62.202 port 51422
2026-03-01T19:39:56.914932+01:00 pingussy sshd-session[3087565]: Invalid user test2 from 134.122.62.202 port 39970
2026-03-01T19:40:40.557392+01:00 pingussy sshd-session[3088038]: Invalid user test3 from 134.122.62.202 port 39308
2026-03-01T19:46:27.678435+01:00 pingussy sshd-session[3091940]: Invalid user postgres from 134.122.62.202 port 56666
2026-03-01T19:47:05.448820+01:00 pingussy sshd-session[3092386]: Invalid user oracle from 134.122.62.202 port 32772
...
show less
Mar 1 18:40:05 VPS sshd[3011284]: Invalid user test2 from 134.122.62.202 port 60054
Mar 1 18:40:05 ...
show moreMar 1 18:40:05 VPS sshd[3011284]: Invalid user test2 from 134.122.62.202 port 60054
Mar 1 18:40:05 VPS sshd[3011284]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.62.202
Mar 1 18:40:05 VPS sshd[3011284]: Invalid user test2 from 134.122.62.202 port 60054
Mar 1 18:40:07 VPS sshd[3011284]: Failed password for invalid user test2 from 134.122.62.202 port 60054 ssh2
Mar 1 18:40:48 VPS sshd[3011404]: Invalid user test3 from 134.122.62.202 port 50838
...
show less
Brute-Force
SSH
Showing 1 to
15
of 99 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩