This IP address has been reported a total of
40
times from
35 distinct
sources.
222.94.30.133 was first reported on
, and the most recent report was
.
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.
Jun 11 02:42:20 routing0302 sshd[2461710]: pam_unix(sshd:auth): authentication failure; logname= uid ...
show moreJun 11 02:42:20 routing0302 sshd[2461710]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.94.30.133 user=root
Jun 11 02:42:22 routing0302 sshd[2461710]: Failed password for root from 222.94.30.133 port 40037 ssh2
Jun 11 02:42:41 routing0302 sshd[2461712]: Invalid user zhangfan from 222.94.30.133 port 40733
...
show less
2026-06-10T03:02:32.677691+00:00 indev sshd[142118]: Invalid user tom from 222.94.30.133 port 40080
...
show more2026-06-10T03:02:32.677691+00:00 indev sshd[142118]: Invalid user tom from 222.94.30.133 port 40080
2026-06-10T03:03:11.600491+00:00 indev sshd[142124]: Connection from 222.94.30.133 port 41241 on 65.108.85.114 port 30123 rdomain ""
2026-06-10T03:03:13.560391+00:00 indev sshd[142124]: Invalid user zhoujun from 222.94.30.133 port 41241
2026-06-10T03:03:30.874893+00:00 indev sshd[142126]: Connection from 222.94.30.133 port 41789 on 65.108.85.114 port 30123 rdomain ""
2026-06-10T03:03:32.278124+00:00 indev sshd[142126]: Invalid user webapp from 222.94.30.133 port 41789
...
show less
2026-06-09T08:35:50.463746+02:00 Travel-Suop sshd[3635698]: Connection from 222.94.30.133 port 39087 ...
show more2026-06-09T08:35:50.463746+02:00 Travel-Suop sshd[3635698]: Connection from 222.94.30.133 port 39087 on 195.201.130.250 port 22123 rdomain ""
2026-06-09T08:35:51.339162+02:00 Travel-Suop sshd[3635698]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.94.30.133 user=root
2026-06-09T08:35:52.848214+02:00 Travel-Suop sshd[3635698]: Failed password for root from 222.94.30.133 port 39087 ssh2
...
show less
Hacking
Brute-Force
Web App Attack
SSH
Anonymous
Jun 8 20:01:11 server20 sshd-session[3989]: User root from 222.94.30.133 not allowed because not li ...
show moreJun 8 20:01:11 server20 sshd-session[3989]: User root from 222.94.30.133 not allowed because not listed in AllowUsers
Jun 8 20:01:34 server20 sshd-session[4195]: Invalid user liuyi from 222.94.30.133 port 39433
Jun 8 20:01:56 server20 sshd-session[4386]: User mysql from 222.94.30.133 not allowed because not listed in AllowUsers
Jun 8 20:02:17 server20 sshd-session[4741]: Invalid user guest from 222.94.30.133 port 40832
Jun 8 20:02:40 server20 sshd-session[4839]: Invalid user scanner from 222.94.30.133 port 41498
...
show less
2026-06-07T14:37:45.314257localhost sshd[50190]: Invalid user jp from 222.94.30.133 port 41708
2026- ...
show more2026-06-07T14:37:45.314257localhost sshd[50190]: Invalid user jp from 222.94.30.133 port 41708
2026-06-07T14:38:10.927161localhost sshd[50192]: Invalid user svn from 222.94.30.133 port 38323
2026-06-07T14:38:35.584885localhost sshd[50196]: Invalid user administrator from 222.94.30.133 port 39034
...
show less
2026-06-05T10:50:05.918212+02:00 aurora sshd[1426704]: Connection closed by 222.94.30.133 port 41740 ...
show more2026-06-05T10:50:05.918212+02:00 aurora sshd[1426704]: Connection closed by 222.94.30.133 port 41740 [preauth]
...
show less
Brute-Force
Anonymous
2026-06-05_03:47:04.75352 User root from 222.94.30.133 not allowed because not listed in AllowUsers
...
show more2026-06-05_03:47:04.75352 User root from 222.94.30.133 not allowed because not listed in AllowUsers
2026-06-05_03:47:26.82027 Invalid user gpadmin from 222.94.30.133 port 41540
show less